Optimization of SeparateSubclassVisitor #297
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi!
We have rather big code-first NH-model in our project with thousand classes and long hierarchy chains.
Testing showed that from two to five minutes are spent on bulding model. Profiling showed thant 70% time is spent in FluentNHibernate, particulary in SeparateSubclassVisitor.IsMapped method.
I suggest a performance fix that optimizes this method. Now our model builds in less than one minute and most time is spent in NH itself.
We are already using this patched version in our project, but it is likely to have it merged with FNH master for updating reasons.
Any comments are welcome, if you need a model and prototype-project with this properties we can provide it.