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
This remain to be seen whether we'll actually need this, but would be worth exploring.
The assumption is that the first few generation will invalidate shared pages rather quickly, as such the peak memory usage at first might get quite high.
A possible solution to this would be to start with a lower number of workers to compensate for the lower CoW effectiveness, and then increase the number of workers of processes with each new generation.
This would mean pitchfork needs a bit of a warm up before achieving peak throughput.
The text was updated successfully, but these errors were encountered:
This remain to be seen whether we'll actually need this, but would be worth exploring.
The assumption is that the first few generation will invalidate shared pages rather quickly, as such the peak memory usage at first might get quite high.
A possible solution to this would be to start with a lower number of workers to compensate for the lower CoW effectiveness, and then increase the number of workers of processes with each new generation.
This would mean pitchfork needs a bit of a warm up before achieving peak throughput.
The text was updated successfully, but these errors were encountered: