Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Determine ideal value for FeatureDataSource default query lookahead #233

Closed
droazen opened this issue Feb 25, 2015 · 1 comment
Closed
Assignees

Comments

@droazen
Copy link
Contributor

droazen commented Feb 25, 2015

DEFAULT_QUERY_LOOKAHEAD_BASES in FeatureDataSource is currently set to 1000. We should empirically determine whether this value results in acceptable performance for typical traversals involving queries over intervals with gradually increasing start/stop positions.

This value controls the number of additional bases by which to expand the END of each query interval that results in a cache miss. Larger values will result in a larger number of cached Features, which will increase the number of cache hits between cache misses, provided query intervals follow the typical pattern of slowly increasing positions. On the other hand, larger values will also increase the cost associated with cache misses, which happen when we jump forward by a large number of bases, switch contigs, or move backwards.

@droazen droazen added the Engine label Feb 25, 2015
@droazen droazen added this to the BlobFish milestone Feb 27, 2015
@droazen droazen self-assigned this Feb 27, 2015
@lbergelson lbergelson modified the milestones: BlobFish, Coelacanth Apr 2, 2015
@akiezun akiezun removed this from the Coelacanth milestone Apr 15, 2015
@akiezun
Copy link
Contributor

akiezun commented Apr 20, 2015

closing this ticket until we determine this is a bottleneck

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants