You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The two KM charts wildly tax the resources of the browser for large samples. Scripting time, measured in profiler, is cut by 60% when we remove them. And peak memory footprint is reduced from 600MB to 300MB.
Rendering points and allowing interactivity is probably not important for this view. Perhaps we can sample and remove tooltips?
The text was updated successfully, but these errors were encountered:
@dippindots product team agreed to getting rid of the censoring crosses and then doing binning. The way binning should work is that we put events into bins by some configurable number of days. We can apply this optimization only when there are more than say, 10k samples.
https://cbioportal.mskcc.org/study/summary?id=mskimpact
The two KM charts wildly tax the resources of the browser for large samples. Scripting time, measured in profiler, is cut by 60% when we remove them. And peak memory footprint is reduced from 600MB to 300MB.
Rendering points and allowing interactivity is probably not important for this view. Perhaps we can sample and remove tooltips?
The text was updated successfully, but these errors were encountered: