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
{{ message }}
This repository has been archived by the owner on Mar 30, 2022. It is now read-only.
for(vari=0;i<MAX_WORKERS;i++){arr[i]=newWorker(CURRENT_DIR+'/lib/workers/worker.js');arr[i].onmessage=function(msg,cb){ ... }}arr[i].onexit=function(code,syssignal){console.log("\033[1;32m#### WORKER TERMINATED, signal %s #####\033[0m",syssignal);};}
My intention is to use long-lived workers and rotate through them (I'm using them for file upload handling). Is this the right approach?
Second, these workers terminate with signal null when server is under heavy load (not file uploads, but just GET /). Why would they do that and how can I figure out why they crash?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I create workers with this bit of code:
My intention is to use long-lived workers and rotate through them (I'm using them for file upload handling). Is this the right approach?
Second, these workers terminate with signal
null
when server is under heavy load (not file uploads, but justGET /
). Why would they do that and how can I figure out why they crash?The text was updated successfully, but these errors were encountered: