Replies: 1 comment 1 reply
-
I doubt that having much data on the heap would be a problem for egui. Are you displaying all those millions of records at the same time? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
First thank you for all your work on this amazing project.
A point in any direction would be helpful.
I have an application that processes tens of millions of data points using async tasks and then caches the results on the heap.
Before filling the heap, my frontend renders at 500+ fps, after my async tasks complete and the results are stored on the heap my fps drop. If I process more tasks I can degrade the front end performance to single digits.
I have narrowed it down to calls to the painter to draw shapes, allocate rects, and the use of labels.
If I disable the panel that draws my main grid I am back at 500+ fps. If I remove the cached items from the heap the performance returns as well.
My app is using around 2gb of ram after processing 100 million records, I would like to know if there is anything I can do to not have
bad UI performance after creating a large heap.
I am guessing its choking on allocation etc. I am trying to make sense of dhat and the flamegraph looking for a silver bullet but no luck yet.
Thanks
Beta Was this translation helpful? Give feedback.
All reactions