зеркало из https://github.com/mozilla/gecko-dev.git
75c9700273
Looking at this code, I'm not sure why I did it like this. We hope that there will be a single optimum nursery size that we can estimate, but the code tries to estimate a growth rate instead. I think this leads to us over-growing the nursery at the start of intensive workloads. The patch changes this the code to estimate an optimum nursery size (in smoothedTargetSize) based on the existing heuristics. This ended up with a slower ramp up of nursery size so I changed it to weight clamped growth factors more when calculating the smoothed value. I tired hard to make this neutral on benchmark results, but I'll guess we'll see. Differential Revision: https://phabricator.services.mozilla.com/D136636 |
||
|---|---|---|
| .. | ||
| ductwork/debugger | ||
| examples | ||
| public | ||
| src | ||
| xpconnect | ||
| app.mozbuild | ||
| ffi.configure | ||
| moz.build | ||
| moz.configure | ||
| sub.configure | ||