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

More than 100 concurrent user makes server very slow #69

Open
jjrjames opened this issue Aug 30, 2018 · 3 comments
Open

More than 100 concurrent user makes server very slow #69

jjrjames opened this issue Aug 30, 2018 · 3 comments

Comments

@jjrjames
Copy link

Hi,
I am using ejaberred latest version with jsxc as client for my project. it is taking too much time while connecting more than 100 concurrent users having 2 or 3 tabs.

Can any one help me is there anything i need to change?
Thanks in advance

@MarcelWaldvogel
Copy link
Contributor

What are your cache-related settings (or all settings, with URL and SECRET anonymized)? What setup are you using? Do you have (anonymized) logs for the XMPP server (related to authentication), xcauth, and Nextcloud (related to JSXC authentication)?

Reasons for slow-down that come to my mind right now:

  • Caching enabled (cache-storage != none) and high cache-bcrypt-rounds
  • The first login for each user with ejabberdctl set (setting the shared roster groups is slow, but is only done when things have changed)
  • Starting each xcauth process from the command line (as was the recommended scenario for xcauth < 2.0) instead of going through the socket interface
  • Slowness of the Nextcloud server

@jjrjames
Copy link
Author

Hi @MarcelWaldvogel thanks for your comment we will check and get back to you.

@MarcelWaldvogel
Copy link
Contributor

Is this still an issue?

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

No branches or pull requests

2 participants