-
Notifications
You must be signed in to change notification settings - Fork 1.6k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to optimize ocelot startup time. #1526
Comments
@raman-m Interesting, how we can test it? Is there any test cases for this thing? Any suggestions? |
@heizel184 are you still facing it on latest versions? |
@heizel184 Dear Hina! Your issue is quite outdated because of legacy version 15.0.6.
Are you sure that all files are valid? So, have all these files valid JSON formatting and syntax?
Deployment can fail because of critical error when starting up the app... |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Hi I am using Ocelot 15.0.6 as a gateway. Since Ocelot supports multiple configuration files. Previously I include seven different configurations files with the routes of different projects API, The problem occurred when a new file is added with more than 80 routes in it. After adding that file The ocelot took too long at startup that the application got stuck and shut down later when deploying gateway.
The current behavior of ocelot is unacceptable, application should not take much time for a startup. How can I optimize that time or speed up the startup time of ocelot at production?
Steps to Reproduce the Problem
Add multiple configuration files with a large no of routes
Specifications
The text was updated successfully, but these errors were encountered: