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

Performance concerns #3

Open
Telavian opened this issue Sep 17, 2020 · 2 comments
Open

Performance concerns #3

Telavian opened this issue Sep 17, 2020 · 2 comments

Comments

@Telavian
Copy link

Telavian commented Sep 17, 2020

I have a 3 node cluster I am using for testing.
CPU: Intel(R) Xeon(R) CPU X5650 @ 2.67GHz
Mem: 94GB
Disk: SSD

Currently doing about 1000 updates a second seems to bring all the nodes to 100% CPU and start timing out operations.
Is this normal?

What should I check or update?

@slater-ben
Copy link

That sounds slow but I guess it depends on the size of the updates as well as could be some configuration issues. I would probably try doing the same inserts on a table without a lucene-based secondary index to see if it's lucene overhead or something else.

@Telavian
Copy link
Author

These updates also were not just on the lucene indexed tables. Either the lucene indexes were bringing the whole cluster down or the non-lucene indexed tables were also slow for some reason.

Certainly switching back to elasticsearch caused the cluster to be very fast again.
I know this information is very general and would love to pin it down to something more specific for you.

Do you have a load test currently?

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