Skip to content
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

Kafdrop too slow #246

Closed
senthil13 opened this issue Mar 5, 2021 · 4 comments · Fixed by #277
Closed

Kafdrop too slow #246

senthil13 opened this issue Mar 5, 2021 · 4 comments · Fixed by #277

Comments

@senthil13
Copy link

Hi Team,

We are using the kafdrop for long time, so far no issues. But when we tried to use against a larger cluster say it has more than 3k topics then the kafdrop home page is too slow to load. We increased the heap/cpu and changed the java parameters too but still we have the slowness. Any suggestion will be appreciated.

$java_home --add-opens=java.base/sun.nio.ch=ALL-UNNAMED -Xms2g -Xmx2g -XX:+UseParallelOldGC -XX:MetaspaceSize=256m -jar $kafdrop_home/$process --zookeeper.connect=$zookeeper_list --kafka.brokerConnect=$kafka_list --schemaregistry.connect=$schema_list --server.port=9000 --topic.deleteEnabled=false --topic.createEnabled=false
Thanks
Senthil

@Wouter86
Copy link

Wouter86 commented Jun 3, 2021

While waiting for support, patching this in may unblock you. It has been proposed via PR but was unfortunately not accepted.

@github-actions
Copy link

github-actions bot commented Jan 7, 2022

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Jan 7, 2022
@github-actions
Copy link

This issue was closed because it has been inactive for 14 days since being marked as stale.

@jorkzijlstra
Copy link
Contributor

I also created a PR to address this slowlyness: #277 but its not moving forward yet

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 a pull request may close this issue.

4 participants