benchmark runtime_error

[chllcy]

./wsb-client-exe --tp 2 --tio 2 --socks-max 100 --socks-port 100 --si 100 --sf 30 --pc 1 -h 192.168.2.28 D |2021-06-09 21:15:39 1623244539526502| Client:add clients for port 20029 D |2021-06-09 21:15:39 1623244539560469| Client:Waiting clients to connect... D |2021-06-09 21:15:39 1623244539560649| Status: SOCKETS: 100 D |2021-06-09 21:15:49 1623244549566251| FRAMES_TOTAL: 25705 D |2021-06-09 21:15:49 1623244549566324| MESSAGES_TOTAL: 25172 D |2021-06-09 21:15:49 1623244549566364| FRAMES_PER_MIN: 154145.374190 D |2021-06-09 21:15:49 1623244549566402| MESSAGES_PER_MIN: 150949.128928 E |2021-06-09 21:15:49 1623244549729510| [oatpp::async::worker::IOEventWorker::setEpollEvent()]:Error. Call to epoll_ctl failed. operation=1, errno=17 terminate called after throwing an instance of 'std::runtime_error' what(): [oatpp::async::worker::IOEventWorker::setEpollEvent()]: Error. Call to epoll_ctl failed. Aborted

[lganzzzo]

Hey @chllcy ,

Thanks for reporting this issue.

Two questions:

• How often you face this issue?
• Are you using the latest oatpp/oatpp-websocket master?

[chllcy]

Hey @chllcy ,

Thanks for reporting this issue.

Two questions:

• How often you face this issue?
• Are you using the latest oatpp/oatpp-websocket master?

1. almost 100%，but the server code is not written by oatpp-websocket。
2. yes,using the latest oatpp/oatpp-websocket master

[lganzzzo]

Hm, interesting,

Is the 3rd party server doing the same thing as the oatpp one? Can you share your server for me to test?