Details
-
Type:
Task
-
Status: To-Do (View Workflow)
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:
-
Story Points:2
-
Epic Link:
-
Sprint:Summer 2019 Sprint 12, Spring 3 : 17 Feb to 28 Feb, Spring 4 : 2 Mar to 13 Mar, Spring 5 : 16 Mar to 27 Mar, Spring 6 : 30 Mar to Apr 10, Spring 8 : 24 Apr to 8 May
Description
Watch this: https://drive.google.com/file/d/1uZHOoVkl-AgQ-jogSGxFH5zulD3wNQeS/view?usp=sharing
The bigwig format is a graph data file format that is supposed to be random access. It contains a "header" at the beginning of the file that maps locations in the file to locations in the genome.
When users open and then click "Load Data" for a small region in the genome, loading the bigwig file's data should feel very fast because IGB only needs to send a byte range request for a small part of the file.
However, this does not seem to be happening.
In fact, the same exact data converted to a different format - tabix-indexed bedgraph - loads much, much faster.
This task is to investigate what is going on. Why is bw file loading so incredibly slow?
Please report what you find as comments in this ticket.
See below comment for example data.
Attachments
Issue Links
- relates to
-
-
- Closed
-