1607259 - Allow configuring the maximum number of running processes

Status: RESOLVED FIXED

(Core Graveyard :: Web Replay, enhancement)

Description

[Brian Hackett [Laid off!]]

The replay control logic has a priority queue which it uses to make sure there are never more than 4 replaying processes operating simultaneously. A fixed number like this isn't appropriate going forward, especially with cloud replay --- the remote machine could have many cores available (up to 96 with AWS) and be able to run many processes simultaneously. The remote machine should be able to inform the control logic how many processes it can spawn, which is simple to do when the remote replaying process reaches the first checkpoint and finishes its primordial manifest. The replaying process can determine this count by querying an environment variable which the cloud service has set. This design also allows the number of processes to be reconfigured when locally replaying, though that will probably only be useful for testing.

Comment 1

[Brian Hackett [Laid off!]]

Attachment: Bug 1607259 - Allow configuring the maximum number of running processes, r=jlast.

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/42a08cd066dc
Allow configuring the maximum number of running processes, r=jlast.

Comment 3

[Dorel Luca [:dluca]]

https://hg.mozilla.org/mozilla-central/rev/42a08cd066dc