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.
For really large iModels or really large changesets, the current PartialECChangeUnifier cannot handle doing it's job while storing all of the elements in memory.
Describe the solution you'd like
Instead, in these extreme cases, the PartialECChangeUnifier can store the changes on disk within the iModel in custom sqlite tables. This will make the processing significantly slower, but it will allow the process to actually finish.
Additional context
A few things still need to be figured out:
How do we determine when we should be storing the changes on-disk versus in-memory. In-memory is significantly faster and totally fine for the large majority of cases, so that should be the preference. Perhaps the user will need to know beforehand to set a boolean to instead process slower, but on-disk?
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
For really large iModels or really large changesets, the current PartialECChangeUnifier cannot handle doing it's job while storing all of the elements in memory.
Describe the solution you'd like
Instead, in these extreme cases, the PartialECChangeUnifier can store the changes on disk within the iModel in custom sqlite tables. This will make the processing significantly slower, but it will allow the process to actually finish.
Describe alternatives you've considered
I have already created a proof of concept that this solution works here: https://github.com/iTwin/itwinjs-core/tree/mattbjordan/disk-based-unifier-poc.
Additional context
A few things still need to be figured out:
The text was updated successfully, but these errors were encountered: