Socket.io .on(message) seems be delayed
up vote
0
down vote
favorite
I have server code like (simplified)
setInterval(longFunction,30);
setInterval(longFunction,30);
function longFunction(){
console.log("longFunction");
doSomethingLong();
}
elsewhere in server code...
socket.on("message",function(){
console.log("message");
})
Problem is that when I send message from client, I can see in server console many many new logs from longFunction and only then I can see log from message.
I want to process message event as soon as possible but it looks that server prefer processing of intervals even multiple times first.
node.js socket.io
asked Nov 22 at 4:07
aqzaqzaqz
1819
|
show 3 more comments
up vote
0
down vote
favorite
I have server code like (simplified)
setInterval(longFunction,30);
setInterval(longFunction,30);
function longFunction(){
console.log("longFunction");
doSomethingLong();
}
elsewhere in server code...
socket.on("message",function(){
console.log("message");
})
Problem is that when I send message from client, I can see in server console many many new logs from longFunction and only then I can see log from message.
I want to process message event as soon as possible but it looks that server prefer processing of intervals even multiple times first.
node.js socket.io
asked Nov 22 at 4:07
aqzaqzaqz
1819
because thosesetIntervalare running in30msinterval even beforedoSomethingLongis done, effectively queueing the CPU for multiple times before any socket message can reach and be processed by server?
– William Chong
Nov 22 at 7:45
but how can I fix it?
– aqzaqzaqz
Nov 26 at 8:50
It depends on what your expected behaviour betweensetInterval,longFunction, and weksocket is, need more context.
– William Chong
Nov 26 at 8:55
I want more priority for message event. If I have message event, process it and run timers later. I changed setInterval to setTimeout and it didn't help. Problem is probably that i have more timers so they run in loop and no other code can be executed.
– aqzaqzaqz
Nov 26 at 9:10
Since javascript is single thread, ifdoSomethingLongis a long running sync function, it cannot be pause/broken in the middle of execution. However what you can od is check if any message event should be processed before runningdoSomethingLong, i.e. in where yourconsole.log("longFunction");is now.
– William Chong
Nov 26 at 10:00
|
show 3 more comments
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have server code like (simplified)
setInterval(longFunction,30);
setInterval(longFunction,30);
function longFunction(){
console.log("longFunction");
doSomethingLong();
}
elsewhere in server code...
socket.on("message",function(){
console.log("message");
})
Problem is that when I send message from client, I can see in server console many many new logs from longFunction and only then I can see log from message.
I want to process message event as soon as possible but it looks that server prefer processing of intervals even multiple times first.
node.js socket.io
asked Nov 22 at 4:07
aqzaqzaqz
1819
I have server code like (simplified)
setInterval(longFunction,30);
setInterval(longFunction,30);
function longFunction(){
console.log("longFunction");
doSomethingLong();
}
elsewhere in server code...
socket.on("message",function(){
console.log("message");
})
Problem is that when I send message from client, I can see in server console many many new logs from longFunction and only then I can see log from message.
I want to process message event as soon as possible but it looks that server prefer processing of intervals even multiple times first.
node.js socket.io
node.js socket.io
asked Nov 22 at 4:07
aqzaqzaqz
1819
asked Nov 22 at 4:07
aqzaqzaqz
1819
asked Nov 22 at 4:07
aqzaqzaqz
1819
asked Nov 22 at 4:07
aqzaqzaqz
1819
asked Nov 22 at 4:07
aqzaqzaqz
1819
1819
because thosesetIntervalare running in30msinterval even beforedoSomethingLongis done, effectively queueing the CPU for multiple times before any socket message can reach and be processed by server?
– William Chong
Nov 22 at 7:45
but how can I fix it?
– aqzaqzaqz
Nov 26 at 8:50
It depends on what your expected behaviour betweensetInterval,longFunction, and weksocket is, need more context.
– William Chong
Nov 26 at 8:55
I want more priority for message event. If I have message event, process it and run timers later. I changed setInterval to setTimeout and it didn't help. Problem is probably that i have more timers so they run in loop and no other code can be executed.
– aqzaqzaqz
Nov 26 at 9:10
Since javascript is single thread, ifdoSomethingLongis a long running sync function, it cannot be pause/broken in the middle of execution. However what you can od is check if any message event should be processed before runningdoSomethingLong, i.e. in where yourconsole.log("longFunction");is now.
– William Chong
Nov 26 at 10:00
|
show 3 more comments
because thosesetIntervalare running in30msinterval even beforedoSomethingLongis done, effectively queueing the CPU for multiple times before any socket message can reach and be processed by server?
– William Chong
Nov 22 at 7:45
but how can I fix it?
– aqzaqzaqz
Nov 26 at 8:50
It depends on what your expected behaviour betweensetInterval,longFunction, and weksocket is, need more context.
– William Chong
Nov 26 at 8:55
I want more priority for message event. If I have message event, process it and run timers later. I changed setInterval to setTimeout and it didn't help. Problem is probably that i have more timers so they run in loop and no other code can be executed.
– aqzaqzaqz
Nov 26 at 9:10
Since javascript is single thread, ifdoSomethingLongis a long running sync function, it cannot be pause/broken in the middle of execution. However what you can od is check if any message event should be processed before runningdoSomethingLong, i.e. in where yourconsole.log("longFunction");is now.
– William Chong
Nov 26 at 10:00
because those
setInterval are running in 30ms interval even before doSomethingLong is done, effectively queueing the CPU for multiple times before any socket message can reach and be processed by server?– William Chong
Nov 22 at 7:45
because those
setInterval are running in 30ms interval even before doSomethingLong is done, effectively queueing the CPU for multiple times before any socket message can reach and be processed by server?– William Chong
Nov 22 at 7:45
but how can I fix it?
– aqzaqzaqz
Nov 26 at 8:50
but how can I fix it?
– aqzaqzaqz
Nov 26 at 8:50
It depends on what your expected behaviour between
setInterval, longFunction, and weksocket is, need more context.– William Chong
Nov 26 at 8:55
It depends on what your expected behaviour between
setInterval, longFunction, and weksocket is, need more context.– William Chong
Nov 26 at 8:55
I want more priority for message event. If I have message event, process it and run timers later. I changed setInterval to setTimeout and it didn't help. Problem is probably that i have more timers so they run in loop and no other code can be executed.
– aqzaqzaqz
Nov 26 at 9:10
I want more priority for message event. If I have message event, process it and run timers later. I changed setInterval to setTimeout and it didn't help. Problem is probably that i have more timers so they run in loop and no other code can be executed.
– aqzaqzaqz
Nov 26 at 9:10
Since javascript is single thread, if
doSomethingLong is a long running sync function, it cannot be pause/broken in the middle of execution. However what you can od is check if any message event should be processed before running doSomethingLong, i.e. in where your console.log("longFunction"); is now.– William Chong
Nov 26 at 10:00
Since javascript is single thread, if
doSomethingLong is a long running sync function, it cannot be pause/broken in the middle of execution. However what you can od is check if any message event should be processed before running doSomethingLong, i.e. in where your console.log("longFunction"); is now.– William Chong
Nov 26 at 10:00
|
show 3 more comments
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53423748%2fsocket-io-onmessage-seems-be-delayed%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
because those
setIntervalare running in30msinterval even beforedoSomethingLongis done, effectively queueing the CPU for multiple times before any socket message can reach and be processed by server?– William Chong
Nov 22 at 7:45
but how can I fix it?
– aqzaqzaqz
Nov 26 at 8:50
It depends on what your expected behaviour between
setInterval,longFunction, and weksocket is, need more context.– William Chong
Nov 26 at 8:55
I want more priority for message event. If I have message event, process it and run timers later. I changed setInterval to setTimeout and it didn't help. Problem is probably that i have more timers so they run in loop and no other code can be executed.
– aqzaqzaqz
Nov 26 at 9:10
Since javascript is single thread, if
doSomethingLongis a long running sync function, it cannot be pause/broken in the middle of execution. However what you can od is check if any message event should be processed before runningdoSomethingLong, i.e. in where yourconsole.log("longFunction");is now.– William Chong
Nov 26 at 10:00