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
Gentics Mesh Version, operating system, or hardware.
v0.10.2
After profiling a migration I noticed that one method was called much more often than expected and took about 15% of the total CPU time during the migration. The method is MicronodeImpl:getParentNode()
This method was called for every field in every micronode or node (about 20k invocations for a migration of about 650 nodes). It is called because HTML fields could need the project name if there is a link which has to be resolved.
There are a few Problems with that method:
The parent is actually not needed at all. It is only used in String/HTML Field transformation if link resolving is performed. And even then, only the project name is fetched from the node.
The algorithm for fetching the node is very inefficient, because it traverses all versions to find the newest version.
This very specific use case causes significant performance issues every time a node is transformed to JSON, which includes every read request for a node and also for schema migration.
The text was updated successfully, but these errors were encountered:
Gentics Mesh Version, operating system, or hardware.
After profiling a migration I noticed that one method was called much more often than expected and took about 15% of the total CPU time during the migration. The method is
MicronodeImpl:getParentNode()
This method was called for every field in every micronode or node (about 20k invocations for a migration of about 650 nodes). It is called because HTML fields could need the project name if there is a link which has to be resolved.
There are a few Problems with that method:
This very specific use case causes significant performance issues every time a node is transformed to JSON, which includes every read request for a node and also for schema migration.
The text was updated successfully, but these errors were encountered: