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
Is your feature request related to a problem? Please describe.
Processes of superordinate processes as for example processes of newspaper years with more than 350 and up to 600 subordinate processes can take up to 20 minutes and more.
Furthermore, corrections in ordering, ... is not possible as for example:
andre-hohmann
changed the title
Improve the time to open superordinate processes with many subordinate processes
Reduce the time to open superordinate processes with many subordinate processes
Feb 21, 2024
I suppose that one of the reasons for the slow performance is, that there are a lot of look ups needed to construct the list although the provided information is not really more than the doctype, id and title of the linked child process. (See: #4925 (reply in thread))
It seems like we do lookups in hundreds of XML files to get minimal information. If i read the code correctly we have to open more than 350 xml files just to get the document type of the children, which - in most cases - is the same for all the children.
Would it maybe be possible to use some of the mechanisms which Hibernate Search offers to display this information way faster? See: #6095 (reply in thread)
Is your feature request related to a problem? Please describe.
Processes of superordinate processes as for example processes of newspaper years with more than 350 and up to 600 subordinate processes can take up to 20 minutes and more.
Furthermore, corrections in ordering, ... is not possible as for example:
Describe the solution you'd like
The time to open the superordinate process and the time to modify the structure tree, ... should be reduced.
Additional context
There has been an issue before, but during the work in the productive system, the need open the processes faster rises again.
The text was updated successfully, but these errors were encountered: