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
Caching of implemented types was added in #426, but was recently removed (commit 3e787da).
It is imperative that caching of implemented interfaces is kept! Profiling ProCoSys with Bifrost 1.0.0.28 takes 30-50 seconds (!) for each request to Bifrost/Security, with most of the time spent inside RuntimeType.GetInterface.
The text was updated successfully, but these errors were encountered:
Looked at the cache when refactoring this and just concluded - that can't be that slow as to need a caching mechanism. And out it went.. 🎱 What I say about the word assume applies here.. It just makes an Ass out of U & Me.
Small update: Most of the seconds spent in Bifrost/Security for us was because of a cache that didn't work properly. But still: Profiling of a small sample useage of the ProCoSys app shows 40% time spent in TypeFinder.FindMultiple, so this is still an important issue.
Caching of implemented types was added in #426, but was recently removed (commit 3e787da).
It is imperative that caching of implemented interfaces is kept! Profiling ProCoSys with Bifrost 1.0.0.28 takes 30-50 seconds (!) for each request to Bifrost/Security, with most of the time spent inside RuntimeType.GetInterface.
The text was updated successfully, but these errors were encountered: