feature request #6554
The details views are newly created with every change of the focus
With every focus change the details view is created completely new. this leads to performance problems.
We should test if it is not possible to reuse certain precomputed details views or details view elements to improve performance
#4 Updated by Patrick Plitzner about 3 years ago
The performance loss is separated in two areas:
- SWT/UI rendering
- can be optimized by caching the UI widgets
- cdm service layer calls
- can be optimized by reducing service calls
- We should also watch out for preference queries that contain service calls like e.g.
#7 Updated by Andreas Müller about 3 years ago
Patrick Plitzner wrote:
Another bottleneck isorg.hibernate.collection.internal.PersistentSet.size() org.hibernate.collection.internal.PersistentSet.iterator()
in some cases taking >90% of the rendering time of the supplemental data view
That is interesting. What exactly is it doing. Loading all data or only 1 request per Set to get the size?
I discussed this with Cherian already if we should have something like a count cache for persistend collections.
Or is it possible to combine the initialization or only the size-request for all supplemental data and not run it instance for instance?