[Libwebsockets] Fast loop of LWS_CALLBACK_GET_THREAD_ID events.
andy at warmcat.com
Sat Apr 25 03:22:40 CEST 2015
On 25 April 2015 10:06:29 GMT+09:00, Andy Green <andy at warmcat.com> wrote:
>On 25 April 2015 03:13:19 GMT+09:00, Bruce Perens <bruce at perens.com>
>>My server currently catches LWS_CALLBACK_GET_THREAD_ID and returns
>>pthread_self(). Currently, it never
>Right but something should be doing so somewhere if it sends anything.
>>Using either the released version or a pull from git today, a
>>libwebsocket_service() loop with a long delay eats the CPU while a
>>is closing. This is what I am seeing:
>>Add poll FD, count = 1 fd = 6, events = 1 *Start of serving a few
>>files via HTML. Lots of LWS_CALLBACK_GET_THREAD_ID events happening
>>Add poll FD, count = 2 fd = 7, events = 1
>>Add poll FD, count = 3 fd = 8, events = 1
>>Add poll FD, count = 4 fd = 9, events = 1
>>Delete poll FD, count = 3 fd = 7, events = 0
>>Delete poll FD, count = 2 fd = 8, events = 0
>>Delete poll FD, count = 1 fd = 9, events = 0
>>Add poll FD, count = 2 fd = 8, events = 1 *Start of Websocket
>>Connection with protocol: radio-server-1 path: /foo
>>Change poll FD fd = 8, events = 5 *Service is in
>Sorry why is he closing? In the interests of reproducing it.
>>state, CPU utilization goes to 100%, continuous
>>Delete poll FD, count = 1 fd = 8, events = 0 Service is closed, CPU
>>utilization goes low again.
>>Websocket connection closed.
>>Am I providing the wrong information to the LWS_CALLBACK_GET_THREAD_ID
>No the number reported there is opaque to lws. Lws itself is truly
>I am sitting in Haneda airport at the moment with a couple of hours to
>kill, I will try to reproduce it.
Just doing this
diff --git a/test-server/test-server.c b/test-server/test-server.c
index 8643c93..ff969ff 100644
@@ -973,7 +973,7 @@ int main(int argc, char **argv)
* the number of ms in the second argument.
- n = libwebsocket_service(context, 50);
+ n = libwebsocket_service(context, 50000);
...and then start and kill the test client after a few seconds does not exhibit the problem. Top shows no load from the server.
Does your scenario actually promote the connection to a ws one or he stays as http only?
>>Libwebsockets mailing list
>>Libwebsockets at ml.libwebsockets.org
>Libwebsockets mailing list
>Libwebsockets at ml.libwebsockets.org
More information about the Libwebsockets