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 Nov 26, 2019. It is now read-only.
Right now many still run on app. Theoretically, when ingesting from S3, all of them could run on jobs -- and even when ingesting from browser upload, more of them could (even without shared storage).
While it would be preferable to have this CPU and disk load on jobs, it may not work out so cleanly in practice, the stack does some weird things. Plus, then we'd need more jobs workers (on single or multiple hosts) to replace the 5 workers currently doing things on our (at the moment) single app server. Ref #1075
The text was updated successfully, but these errors were encountered:
Right now many still run on
app
. Theoretically, when ingesting from S3, all of them could run onjobs
-- and even when ingesting from browser upload, more of them could (even without shared storage).While it would be preferable to have this CPU and disk load on
jobs
, it may not work out so cleanly in practice, the stack does some weird things. Plus, then we'd need morejobs
workers (on single or multiple hosts) to replace the 5 workers currently doing things on our (at the moment) singleapp
server. Ref #1075The text was updated successfully, but these errors were encountered: