Multi-threaded load/save database

Open
#7,799 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
28/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp
Domain
database, performance

Research direction

No files, tests, or entry points are named. Start by locating the database load/save implementation and measuring opening time for a large binary; determine whether the bottleneck is parallelizable or needs another optimization. Done should mean a verified improvement without compromising database correctness.

Written by the indexing model from the issue text.

Description

What is the feature you'd like to have?
For now load/save database happen in single thread.
Image
I don't know how hard from technical aspect parallelize this, but for big binaries, opening happens for 3-5 minutes, and would be excellent if it could be optimized. But you can freely close this issue if it's not possible from technical aspect.

Are any alternative solutions acceptable?
Any other optimizations for opening large binaries database.

Dominant language
C++
Stars
1.3k
Forks
298
Avg merge
5d 5h
Merged PRs (30d)
19

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Vector35/binaryninja-api

All issues in Vector35/binaryninja-api

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.