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
{{ message }}
This repository has been archived by the owner on Jun 26, 2021. It is now read-only.
I am working on a project that generates ~2500 resources, each file has a number of references. I have noticed that emfjson is very slow to load ~30mins, compared to the default XMLResource. Would it be possible to add something like OPTION_DEFER_IDREF_RESOLUTION described below.
This option can be enabled to defer resolving references within a resource until the whole document has been parsed. The default strategy is to try to resolve each reference as it is encountered and then, at the end, resolve any ones that failed. This wastes time looking up forward references that do not exist yet, which, if you're using intrinsic IDs, can involve iterating over every object in the resource.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am working on a project that generates ~2500 resources, each file has a number of references. I have noticed that emfjson is very slow to load ~30mins, compared to the default XMLResource. Would it be possible to add something like OPTION_DEFER_IDREF_RESOLUTION described below.
https://www.eclipse.org/modeling/emf/docs/performance/EMFPerformanceTips.html
OPTION_DEFER_IDREF_RESOLUTION
Option value: Boolean.
This option can be enabled to defer resolving references within a resource until the whole document has been parsed. The default strategy is to try to resolve each reference as it is encountered and then, at the end, resolve any ones that failed. This wastes time looking up forward references that do not exist yet, which, if you're using intrinsic IDs, can involve iterating over every object in the resource.
The text was updated successfully, but these errors were encountered: