Skip to content

Conversation

@ggrote
Copy link

@ggrote ggrote commented Jan 9, 2023

I came across the issue of a very long request to signalr/start, taking around 50 seconds in our application. While trying to fix the problem I thought about giving SignalR a list of assemblies to scan for hubs instead of scanning all assemblies in our project including all libraries we use.

But setting a new Activator for IAssemblyLocator in the DependencyResolver did not have any effect at all. So I digged deeper into the sourcecode of SignalR and found out that the OwinExtension overrides any custom IAssemblyLocator.

This should also fix the problem in issue #4582.
The startup time for SignalR decreased from around 50s to 302ms.

@ghost
Copy link

ghost commented Jan 9, 2023

CLA assistant check
All CLA requirements met.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants