what deffrentce beetween serverpeer and ClientSDK for performance test.
Options
Masa
✭
I'm developing load test.
and looking at performance test.
https://doc.photonengine.com/zh-cn/onpremise/current/performance/performance-tests
It's says
"But if you try to build a "load test client" with Photon's Client SDKs, the clients will be the bottleneck and you will get bad, misleading results."
now I'm wonduling what deffrentce beetween serverpeer and ClientSDK.
because I want to make a Real Performance test (I will use couple of server for client)
could you tell me advantage or disadvantage or any limitation as well.
and looking at performance test.
https://doc.photonengine.com/zh-cn/onpremise/current/performance/performance-tests
It's says
"But if you try to build a "load test client" with Photon's Client SDKs, the clients will be the bottleneck and you will get bad, misleading results."
now I'm wonduling what deffrentce beetween serverpeer and ClientSDK.
because I want to make a Real Performance test (I will use couple of server for client)
could you tell me advantage or disadvantage or any limitation as well.
0
Comments
-
Servers limit the amount of data each client can send per second. I'm assuming this is for the safety of the server not getting psuedo-DDOSed. Using a server-to-server peer instead removes this limitation as it's assumed servers won't be DDOSing other servers.0
-
hi, there
actually main reason is basic architecture. Client lib creates thread to work with socket. so, if you have 1000 sockets 1000 threads will be created. it is very difficult for operation system to manage this amount of threads and if you are going to start even more then it will be even worse.
server peer does not use dedicated thread. it uses thread pool. so much more peers might be handled by system
best,
ilya1 -
I get the point.
Thank you for your explanation.0