-
Notifications
You must be signed in to change notification settings - Fork 408
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 testing #605
Comments
Hard to say... You could try to use https://visualvm.github.io/ to search hotspot. |
Redis,and do not use DTLS |
If the num of requests is to large,what will leshan do?the request will be pushed to a set or list,wait to process? |
What do you mean by "num of request is too large" ? Request is store in memory until it was handled. AFAIK, there is not numeric limit, the only limit is memory available. |
Thank u for your answer. I find the 'RedisLock' in the file 'leshan/leshan-server-cluster/src/main/java/org/eclipse/leshan/server/cluster/RedisRegistrationStore.java' In my test, my server cluster'sperformance becomes worse maybe becouse of it. |
I'm currently not aware about performance issue about RedisLock. This #623 could maybe cause performance issue, did you test with the last version of Leshan which fix this issue ? |
I'm not sure to know where we are about this issue :) Should we close it ? |
I find a problem while performance testing.
I simulated 100 thousand clients to register to leshan server by 500 register request per second.
I find the response will become slower and slower,about 20s In the worst case.
I don't know what is wrong with my leshan server.
the leshan server :4CPU,8G memory
and the redis server:2CPU,4G memory
Add one point,after one client's successful registation, the server will send a observe request to the client.
The text was updated successfully, but these errors were encountered: