-
Notifications
You must be signed in to change notification settings - Fork 78
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
3 changed files
with
31 additions
and
25 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,2 @@ | ||
* BundleData::__refseq__ and BundleData::__gseq__ should be bundled together as a shared pointer to a reference seq data structure (e.g. similar to `GRefData`) , _reference counted_ , as in a multi-threaded environment there could be many/multiple bundles sharing that info and it is wasteful to duplicate it for every bundle | ||
|
||
* we should get rid of that terrible hashing hack (appending a dummy suffix, `id+=`) in `rlink.cpp` processRead(), by using a better hash function | ||
|
||
* implement a better SPMC threading model with less locking -- perhaps one with a queue per consumer/worker? However, multiple small bundles should be packaged together (say 100 tiny bundles at once) and passed on to a worker thread all at once. | ||
* implement a better SPMC threading model with less locking. Multiple small bundles should be packaged together (say 50 tiny bundles at once), with a dynamic limit based on the total number of junctions across the bundles, and passed on to a worker thread all at once. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters