Loading Profile...
Performance Optimizations
Hi!
I am currently looking for places to improve performance. Profiling a simple project resulted in 80% of the processing time being spent on rendering.
I have optimized one or two functions, where typecasts were evitable, but this only accounted for less than a percent of performance.
Do you have any idea where i could optimize the project further?
I am currently looking for places to improve performance. Profiling a simple project resulted in 80% of the processing time being spent on rendering.
I have optimized one or two functions, where typecasts were evitable, but this only accounted for less than a percent of performance.
Do you have any idea where i could optimize the project further?
I’m optimistic
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
-
Inappropriate?Claudius,
What's your take on the 80% spent on rendering?! :)
For me it seems good, after all OpenZoom is mostly about rendering. Good question regarding optimisation opportunities. Currently, most of the heavy-lifting is done in the ImagePyramidRenderManager::updateDisplayList() method. Besides that, I've wanted to optimize the cache implementation for a long time now. Currently, the cache eviction mechanism runs in O(n) but if we'd use a linked list we could bring that down to O(1) for every access and eviction. Additionally, I've come to the conclusion that ideally the cache shouldn't rely on the number of items but rather on how many pixels it stores.
What do you think?
Cheers,
Daniel
I’m thankful
EMPLOYEE
