Details
-
Type: Task
-
Status: Closed (View Workflow)
-
Priority: Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Story Points:2
-
Epic Link:
-
Sprint:Spring 3, Spring 4, Spring 5
Description
Goal: Determine if IGB can run faster and better in JDK21 versus JDK8?
Ideas for stress-testing IGB:
- Users have noticed that when several genome graphs are loaded across an entire chromosome, scrolling and zooming gets a bit laggy. This is due to the large number of computations that have to happen to display a large amount of data during navigation. This could be a way to investigate improvements in speed.
- Another way to answer this question would be to investigate how memory management may have improved - or not - with the release of JDK21. When a user loads data into IGB, IGB displays in the bottom right corner information about how much memory IGB is using. It's possible that we are now able to load more data into IGB thanks to improvements in Java. For example, you could load the same data into IGB 10 and IGB 9 and observe whether the number reporting memory usage is different, or not.
Other thoughts on this:
- Possibility to write a testing script and time IGB
- NF: comments that we need this to be repeatable.
- AL: to start, create a narrative describing what you would do to investigate. Fore example, you could use the RNA-Seq coverage graphs from human genome, using the MEOX1 scenario as starting point. See: https://www.slideshare.net/AnnLoraine/use-integrated-genome-browser-to-explore-analyze-and-publish-genomic-data. Example: Load a scaled coverage graph for each data set for chromosome 1 of the human genome and then observe if IGB responsiveness changes as you pan and zoom through the data. An example task that a user might actually want to do with data like this would be to search visually for differentially expressed genes across the chromosome (or genome). Once all the genome graphs (coverage graphs) are scaled the same, places where peaks are noticeably different in height represent differentially expressed genes. Note that the dogma about differential expression analysis is that you need statistical inference methods to detect DE genes. But probably this is not entirely true for genes that are VERY differentially expressed (e.g., > 2x) in part because genes with BIG differences in expression are probably the most important biologically.
- Question: Should we investigate this on every platform? AL's opinion: check to see if there are BIG differences between the platforms.
Attachments
Issue Links
Activity
Ann Loraine
created issue -
Ann Loraine
made changes -
Field | Original Value | New Value |
---|---|---|
Description |
Goal: Determine if IGB can run faster and better in JDK21 versus JDK8?
Ideas for stress-testing IGB: Users have noticed that when several genome graphs are loaded across an entire chromosome, scrolling and zooming gets a bit laggy. This is due to the large number of computations that have to happen to display a large amount of data during navigation. This could be a way to investigate improvements in speed. |
Goal: Determine if IGB can run faster and better in JDK21 versus JDK8?
Ideas for stress-testing IGB: * Users have noticed that when several genome graphs are loaded across an entire chromosome, scrolling and zooming gets a bit laggy. This is due to the large number of computations that have to happen to display a large amount of data during navigation. This could be a way to investigate improvements in speed. * Another way to answer this question would be to investigate how memory management may have improved - or not - with the release of JDK21. When a user loads data into IGB, IGB displays in the bottom right corner information about how much memory IGB is using. It's possible that we are now able to load more data into IGB thanks to improvements in Java. For example, you could load the same data into IGB 10 and IGB 9 and observe whether the number reporting memory usage is different, or not. |
Ann Loraine
made changes -
Description |
Goal: Determine if IGB can run faster and better in JDK21 versus JDK8?
Ideas for stress-testing IGB: * Users have noticed that when several genome graphs are loaded across an entire chromosome, scrolling and zooming gets a bit laggy. This is due to the large number of computations that have to happen to display a large amount of data during navigation. This could be a way to investigate improvements in speed. * Another way to answer this question would be to investigate how memory management may have improved - or not - with the release of JDK21. When a user loads data into IGB, IGB displays in the bottom right corner information about how much memory IGB is using. It's possible that we are now able to load more data into IGB thanks to improvements in Java. For example, you could load the same data into IGB 10 and IGB 9 and observe whether the number reporting memory usage is different, or not. |
Goal: Determine if IGB can run faster and better in JDK21 versus JDK8?
Ideas for stress-testing IGB: * Users have noticed that when several genome graphs are loaded across an entire chromosome, scrolling and zooming gets a bit laggy. This is due to the large number of computations that have to happen to display a large amount of data during navigation. This could be a way to investigate improvements in speed. * Another way to answer this question would be to investigate how memory management may have improved - or not - with the release of JDK21. When a user loads data into IGB, IGB displays in the bottom right corner information about how much memory IGB is using. It's possible that we are now able to load more data into IGB thanks to improvements in Java. For example, you could load the same data into IGB 10 and IGB 9 and observe whether the number reporting memory usage is different, or not. Other thoughts on this: * Possibility to write a testing script and time IGB * NF: comments that we need this to be repeatable. * AL: to start, create a narrative describing what you would do to investigate. Fore example, you could use the RNA-Seq coverage graphs from human genome, using the MEOX1 scenario as starting point. |
Ann Loraine
made changes -
Description |
Goal: Determine if IGB can run faster and better in JDK21 versus JDK8?
Ideas for stress-testing IGB: * Users have noticed that when several genome graphs are loaded across an entire chromosome, scrolling and zooming gets a bit laggy. This is due to the large number of computations that have to happen to display a large amount of data during navigation. This could be a way to investigate improvements in speed. * Another way to answer this question would be to investigate how memory management may have improved - or not - with the release of JDK21. When a user loads data into IGB, IGB displays in the bottom right corner information about how much memory IGB is using. It's possible that we are now able to load more data into IGB thanks to improvements in Java. For example, you could load the same data into IGB 10 and IGB 9 and observe whether the number reporting memory usage is different, or not. Other thoughts on this: * Possibility to write a testing script and time IGB * NF: comments that we need this to be repeatable. * AL: to start, create a narrative describing what you would do to investigate. Fore example, you could use the RNA-Seq coverage graphs from human genome, using the MEOX1 scenario as starting point. |
Goal: Determine if IGB can run faster and better in JDK21 versus JDK8?
Ideas for stress-testing IGB: * Users have noticed that when several genome graphs are loaded across an entire chromosome, scrolling and zooming gets a bit laggy. This is due to the large number of computations that have to happen to display a large amount of data during navigation. This could be a way to investigate improvements in speed. * Another way to answer this question would be to investigate how memory management may have improved - or not - with the release of JDK21. When a user loads data into IGB, IGB displays in the bottom right corner information about how much memory IGB is using. It's possible that we are now able to load more data into IGB thanks to improvements in Java. For example, you could load the same data into IGB 10 and IGB 9 and observe whether the number reporting memory usage is different, or not. Other thoughts on this: * Possibility to write a testing script and time IGB * NF: comments that we need this to be repeatable. * AL: to start, create a narrative describing what you would do to investigate. Fore example, you could use the RNA-Seq coverage graphs from human genome, using the MEOX1 scenario as starting point. See: https://www.slideshare.net/AnnLoraine/use-integrated-genome-browser-to-explore-analyze-and-publish-genomic-data |
Ann Loraine
made changes -
Description |
Goal: Determine if IGB can run faster and better in JDK21 versus JDK8?
Ideas for stress-testing IGB: * Users have noticed that when several genome graphs are loaded across an entire chromosome, scrolling and zooming gets a bit laggy. This is due to the large number of computations that have to happen to display a large amount of data during navigation. This could be a way to investigate improvements in speed. * Another way to answer this question would be to investigate how memory management may have improved - or not - with the release of JDK21. When a user loads data into IGB, IGB displays in the bottom right corner information about how much memory IGB is using. It's possible that we are now able to load more data into IGB thanks to improvements in Java. For example, you could load the same data into IGB 10 and IGB 9 and observe whether the number reporting memory usage is different, or not. Other thoughts on this: * Possibility to write a testing script and time IGB * NF: comments that we need this to be repeatable. * AL: to start, create a narrative describing what you would do to investigate. Fore example, you could use the RNA-Seq coverage graphs from human genome, using the MEOX1 scenario as starting point. See: https://www.slideshare.net/AnnLoraine/use-integrated-genome-browser-to-explore-analyze-and-publish-genomic-data |
Goal: Determine if IGB can run faster and better in JDK21 versus JDK8?
Ideas for stress-testing IGB: * Users have noticed that when several genome graphs are loaded across an entire chromosome, scrolling and zooming gets a bit laggy. This is due to the large number of computations that have to happen to display a large amount of data during navigation. This could be a way to investigate improvements in speed. * Another way to answer this question would be to investigate how memory management may have improved - or not - with the release of JDK21. When a user loads data into IGB, IGB displays in the bottom right corner information about how much memory IGB is using. It's possible that we are now able to load more data into IGB thanks to improvements in Java. For example, you could load the same data into IGB 10 and IGB 9 and observe whether the number reporting memory usage is different, or not. Other thoughts on this: * Possibility to write a testing script and time IGB * NF: comments that we need this to be repeatable. * AL: to start, create a narrative describing what you would do to investigate. Fore example, you could use the RNA-Seq coverage graphs from human genome, using the MEOX1 scenario as starting point. See: https://www.slideshare.net/AnnLoraine/use-integrated-genome-browser-to-explore-analyze-and-publish-genomic-data. Example: Load a scaled coverage graph for each data set for chromosome 1 of the human genome and then observe if IGB responsiveness changes as you pan and zoom through the data. An example task that a user might actually want to do with data like this would be to search visually for differentially expressed genes across the chromosome (or genome). Once all the genome graphs (coverage graphs) are scaled the same, places where peaks are noticeably different in height represent differentially expressed genes. Note that the dogma about differential expression analysis is that you need statistical inference methods to detect DE genes. But probably this is not entirely true for genes that are VERY differentially expressed (e.g., > 2x) in part because genes with BIG differences in expression are probably the most important biologically. |
Ann Loraine
made changes -
Description |
Goal: Determine if IGB can run faster and better in JDK21 versus JDK8?
Ideas for stress-testing IGB: * Users have noticed that when several genome graphs are loaded across an entire chromosome, scrolling and zooming gets a bit laggy. This is due to the large number of computations that have to happen to display a large amount of data during navigation. This could be a way to investigate improvements in speed. * Another way to answer this question would be to investigate how memory management may have improved - or not - with the release of JDK21. When a user loads data into IGB, IGB displays in the bottom right corner information about how much memory IGB is using. It's possible that we are now able to load more data into IGB thanks to improvements in Java. For example, you could load the same data into IGB 10 and IGB 9 and observe whether the number reporting memory usage is different, or not. Other thoughts on this: * Possibility to write a testing script and time IGB * NF: comments that we need this to be repeatable. * AL: to start, create a narrative describing what you would do to investigate. Fore example, you could use the RNA-Seq coverage graphs from human genome, using the MEOX1 scenario as starting point. See: https://www.slideshare.net/AnnLoraine/use-integrated-genome-browser-to-explore-analyze-and-publish-genomic-data. Example: Load a scaled coverage graph for each data set for chromosome 1 of the human genome and then observe if IGB responsiveness changes as you pan and zoom through the data. An example task that a user might actually want to do with data like this would be to search visually for differentially expressed genes across the chromosome (or genome). Once all the genome graphs (coverage graphs) are scaled the same, places where peaks are noticeably different in height represent differentially expressed genes. Note that the dogma about differential expression analysis is that you need statistical inference methods to detect DE genes. But probably this is not entirely true for genes that are VERY differentially expressed (e.g., > 2x) in part because genes with BIG differences in expression are probably the most important biologically. |
Goal: Determine if IGB can run faster and better in JDK21 versus JDK8?
Ideas for stress-testing IGB: * Users have noticed that when several genome graphs are loaded across an entire chromosome, scrolling and zooming gets a bit laggy. This is due to the large number of computations that have to happen to display a large amount of data during navigation. This could be a way to investigate improvements in speed. * Another way to answer this question would be to investigate how memory management may have improved - or not - with the release of JDK21. When a user loads data into IGB, IGB displays in the bottom right corner information about how much memory IGB is using. It's possible that we are now able to load more data into IGB thanks to improvements in Java. For example, you could load the same data into IGB 10 and IGB 9 and observe whether the number reporting memory usage is different, or not. Other thoughts on this: * Possibility to write a testing script and time IGB * NF: comments that we need this to be repeatable. * AL: to start, create a narrative describing what you would do to investigate. Fore example, you could use the RNA-Seq coverage graphs from human genome, using the MEOX1 scenario as starting point. See: https://www.slideshare.net/AnnLoraine/use-integrated-genome-browser-to-explore-analyze-and-publish-genomic-data. Example: Load a scaled coverage graph for each data set for chromosome 1 of the human genome and then observe if IGB responsiveness changes as you pan and zoom through the data. An example task that a user might actually want to do with data like this would be to search visually for differentially expressed genes across the chromosome (or genome). Once all the genome graphs (coverage graphs) are scaled the same, places where peaks are noticeably different in height represent differentially expressed genes. Note that the dogma about differential expression analysis is that you need statistical inference methods to detect DE genes. But probably this is not entirely true for genes that are VERY differentially expressed (e.g., > 2x) in part because genes with BIG differences in expression are probably the most important biologically. * Question: Should we investigate this on every platform? AL's opinion: check to see if there are BIG differences between the platforms. |
Ann Loraine
made changes -
Epic Link | IGBF-3142 [ 21688 ] |
Ann Loraine
made changes -
Sprint | Spring 3 [ 187 ] |
Ann Loraine
made changes -
Rank | Ranked higher |
Nowlan Freese
made changes -
Attachment | test.igb [ 18199 ] |
Paige Kulzer
made changes -
Assignee | Paige Kulzer [ pkulzer ] |
Paige Kulzer
made changes -
Status | To-Do [ 10305 ] | In Progress [ 3 ] |
Paige Kulzer
made changes -
Attachment | StressTest.igb [ 18200 ] |
Paige Kulzer
made changes -
Nowlan Freese
made changes -
Comment | [ I tested the StressTest.igb script on Windows and saw the same error. ] |
Paige Kulzer
made changes -
Status | In Progress [ 3 ] | To-Do [ 10305 ] |
Ann Loraine
made changes -
Sprint | Spring 3 [ 187 ] | Spring 3, Spring 4 [ 187, 188 ] |
Ann Loraine
made changes -
Rank | Ranked higher |
Paige Kulzer
made changes -
Attachment | StressTest_Expanded.igb [ 18239 ] |
Paige Kulzer
made changes -
Status | To-Do [ 10305 ] | In Progress [ 3 ] |
Paige Kulzer
made changes -
Attachment | A_thaliana_Jun_2009_Chr1.bam.bai [ 18257 ] | |
Attachment | A_thaliana_Jun_2009_Chr1.bam [ 18258 ] |
Paige Kulzer
made changes -
Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
Paige Kulzer
made changes -
Assignee | Paige Kulzer [ pkulzer ] |
Ann Loraine
made changes -
Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
Ann Loraine
made changes -
Status | First Level Review in Progress [ 10301 ] | Ready for Pull Request [ 10304 ] |
Ann Loraine
made changes -
Assignee | Ann Loraine [ aloraine ] |
Paige Kulzer
made changes -
Ann Loraine
made changes -
Sprint | Spring 3, Spring 4 [ 187, 188 ] | Spring 3, Spring 4, Spring 5 [ 187, 188, 189 ] |
Ann Loraine
made changes -
Rank | Ranked higher |
Ann Loraine
made changes -
Status | Ready for Pull Request [ 10304 ] | Pull Request Submitted [ 10101 ] |
Ann Loraine
made changes -
Status | Pull Request Submitted [ 10101 ] | Reviewing Pull Request [ 10303 ] |
Ann Loraine
made changes -
Status | Reviewing Pull Request [ 10303 ] | Merged Needs Testing [ 10002 ] |
Ann Loraine
made changes -
Assignee | Ann Loraine [ aloraine ] |
Ann Loraine
made changes -
Status | Merged Needs Testing [ 10002 ] | Post-merge Testing In Progress [ 10003 ] |
Ann Loraine
made changes -
Resolution | Done [ 10000 ] | |
Status | Post-merge Testing In Progress [ 10003 ] | Closed [ 6 ] |
Ann Loraine
made changes -
Assignee | Paige Kulzer [ pkulzer ] |