RESOLVED FIXED 170678
webkitpy: Increase estimate for processes run by iOS Simulators
https://bugs.webkit.org/show_bug.cgi?id=170678
Summary webkitpy: Increase estimate for processes run by iOS Simulators
Jonathan Bedard
Reported 2017-04-10 09:38:39 PDT
Previously, it was estimated that each simulated iOS device would run 100 processes. With newer version of iOS, this is closer to 125.
Attachments
Patch (1.53 KB, patch)
2017-04-10 09:43 PDT, Jonathan Bedard
no flags
Patch for landing (1.53 KB, patch)
2017-04-10 10:43 PDT, Jonathan Bedard
no flags
Radar WebKit Bug Importer
Comment 1 2017-04-10 09:39:55 PDT
Jonathan Bedard
Comment 2 2017-04-10 09:43:46 PDT
Aakash Jain
Comment 3 2017-04-10 09:53:20 PDT
Comment on attachment 306693 [details] Patch looks good to me.
Jonathan Bedard
Comment 4 2017-04-10 10:00:04 PDT
Will commit queue once EWS comes back clean.
Jonathan Bedard
Comment 5 2017-04-10 10:43:13 PDT
Created attachment 306708 [details] Patch for landing
WebKit Commit Bot
Comment 6 2017-04-10 11:12:00 PDT
Comment on attachment 306708 [details] Patch for landing Clearing flags on attachment: 306708 Committed r215191: <http://trac.webkit.org/changeset/215191>
WebKit Commit Bot
Comment 7 2017-04-10 11:12:04 PDT
All reviewed patches have been landed. Closing bug.
Alexey Proskuryakov
Comment 8 2017-04-10 21:13:50 PDT
Will we also change the plist on the wiki to allow for more files?
Jonathan Bedard
Comment 9 2017-04-11 08:19:33 PDT
Talking with Aakash yesterday, this is likely not the only change we need. We should consider re-doing the tests he did to determine the optimal number of simulators to run. He sent me his measurements from awhile back, on newer simulators, I suspect somewhere around 8 is optimal, as opposed to 12. We haven't seen the file cap be an issue.
Aakash Jain
Comment 10 2017-04-11 08:22:09 PDT
(In reply to Alexey Proskuryakov from comment #8) > Will we also change the plist on the wiki to allow for more files? both the plist files are still good, since they increase the process, file limits significantly. The change in this bug is very minor.
Note You need to log in before you can comment on or make changes to this bug.