You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Number of port limitation:
Using several clients on the same machine may reach to the limit of available ports. (see : #1406 (comment))
A solution could be to implement queue mode and so sleeping client could free IP port and so you will be able to simulate more client by machine but the maximum of client talking at the same time is still limited by the maximum number of port (~35k).
About thread limitation, using https://github.com/golioth/xk6-coap, which is Go-based (a similar solution to Java 21 virtual threads), will overcome this (with some extra benefits of the k6 performance framework)
Another solution for the number of ports is to run multiple interfaces on the client machine because the 16-bit port limitation is a per-interface limitation. I wonder if you can do this by running one docker container for the server and multiple docker containers for the client and keeping the traffic in the docker network.
Also, you can get more ports per interface by changing this kernel parameter: /proc/sys/net/ipv4/ip_local_port_range
Example: echo 10000 64000 > /proc/sys/net/ipv4/ip_local_port_range
About thread limitation, using https://github.com/golioth/xk6-coap, which is Go-based (a similar solution to Java 21 virtual threads), will overcome this (with some extra benefits of the k6 performance framework)
Tell, me If I misunderstood : this is an alternative of "Using Leshan library to simulate several clients", if you use it then you don't use Leshan client at all ?
Yes you are right. When I need to do these kinds of tests I often need to simulate the CoAP part (for example the registration) and also use some HTTP API to verify things on the server or trigger more commands like LWM2M reads. So that's why I'm exploring this way of load testing CoAP/LWM2M servers.
This issue aims to centralize information about using Leshan to simulate several clients.
Here is known issue, generally this is about using too many thread:
UDPConnector
of californium need at least 2 thread by clientDTLSConnector
of californium need at least 1 thread by clientDefaultRegistrationEngine
blocking issuePossible solution/workaround about using too many thread:
Number of port limitation:
Using several clients on the same machine may reach to the limit of available ports. (see : #1406 (comment))
A solution could be to implement queue mode and so sleeping client could free IP port and so you will be able to simulate more client by machine but the maximum of client talking at the same time is still limited by the maximum number of port (~35k).
Here is old issue related to that:
Here is a tool which aims to to that : https://github.com/sbernard31/benchmark-clients
(Content of this issue will be updated when we get new information)
The text was updated successfully, but these errors were encountered: