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 testing #605

Closed
bujingyun8 opened this issue Nov 6, 2018 · 7 comments
Closed

 performance testing #605

bujingyun8 opened this issue Nov 6, 2018 · 7 comments
Labels
question Any question about leshan

Comments

@bujingyun8
Copy link

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.

@sbernard31
Copy link
Contributor

Hard to say...
Which kind of RegistrationStore are you using ? Are you using DTLS ?

You could try to use https://visualvm.github.io/ to search hotspot.

@sbernard31 sbernard31 added the question Any question about leshan label Nov 6, 2018
@bujingyun8
Copy link
Author

Redis,and do not use DTLS

@bujingyun8
Copy link
Author

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?

@sbernard31
Copy link
Contributor

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.

@bujingyun8
Copy link
Author

Thank u for your answer.
Now I find some other troubles.

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.

@sbernard31
Copy link
Contributor

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 ?

@sbernard31
Copy link
Contributor

I'm not sure to know where we are about this issue :)

Should we close it ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Any question about leshan
Projects
None yet
Development

No branches or pull requests

2 participants