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
After investigation of the below query, it's become apparent that the use of cloneDeep in any function which is expected to be called many times in quick succession, or is expected to perform transformations on large objects, i.e. _createBTEEdges(), is more-or-less bound to cause performance issues (both in responsiveness and overall resource use).
It would probably be worthwhile to figure out how best to change the internal flow of data such that any current uses can be removed. Currently all uses are in qedge2bteedge.
The following query causes server crash due to out-of-memory exception while cloning:
After investigation of the below query, it's become apparent that the use of
cloneDeep
in any function which is expected to be called many times in quick succession, or is expected to perform transformations on large objects, i.e._createBTEEdges()
, is more-or-less bound to cause performance issues (both in responsiveness and overall resource use).It would probably be worthwhile to figure out how best to change the internal flow of data such that any current uses can be removed. Currently all uses are in qedge2bteedge.
The following query causes server crash due to out-of-memory exception while cloning:
The text was updated successfully, but these errors were encountered: