-
Notifications
You must be signed in to change notification settings - Fork 859
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
UI or API calls taking more than 15 minutes to load #233
Comments
Same here, in my case takes 4 minutes to load, meanwhile this issue is not fixed, is there a version that doesn't behave like this? |
I "fixed" it by increasing the resources. But that's not a real fix :( |
Tried to increase the heap size, but the perform hasn't change. How did you setup yours? |
@kevincoelho1989 |
I too has the same issue, Even I increased to heap but no improvement. one thing i noticed is kafdrop is fast when the total topic count is less than 500, if its more than ~ 650 + then its really slow. |
I have 736 topics and it takes a painful 1 minute, 7 seconds to load consistently. Even if I refresh the page, it takes almost exactly the same amount of time. I tried playing with JVM_OPTS settings, but did not seem to make any difference. |
This issue is stale because it has been open for 30 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
I actually created a PR to tackle this issue: #277 but its not moving forward yet |
Hi all,
when I deploy locally Kafdrop and access the UI, it takes more than 3 minutes to load the UI. If I make a request to the kafdrop API takes more or less the same time. Since I've seen no one mentioning this, I'm starting to think that is something I did wrong.
Is there any troubleshooting guide or a DEBUG mode to see what could be causing this?
The kafdrop logs are not showing any errors. Here are the screenshots of the browser developer tools and postman:
The errors in the browser are:
And the kafdrop logs just show:
The text was updated successfully, but these errors were encountered: