Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upSet a reasonable max count on open files and don't panic if set fails #7992
Conversation
|
Reviewed 1 of 1 files at r1. components/script/lib.rs, line 106 [r1] (raw file): Comments from the review on Reviewable.io |
|
|
|
Yes, I saw that. I picked 4096 because of the extra parallelization in servo and didn't see any harm in requesting a higher limit (doesn't mean we'll use it). I was originally thinking 1024, but we can default to 800 if you want, as long we you think it's enough. Before we were requesting the max possible, which at least on my laptop was 65536. The ARM system I'm testing on has a max of 4096 and a default of 1024. |
|
I'm a little worried about http://mxr.mozilla.org/mozilla-central/source/netwerk/base/nsSocketTransportService2.cpp#1432, which uses 'at least', implying only 1k somewhere? Maybe @vvuk can comment - did you run into anything with |
|
FYI, this |
|
Hrm, yeah, let's just stick with 4096, then, and see how it works out. @bors-servo r+ |
|
|
…gstrom Set a reasonable max count on open files and don't panic if set fails <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/7992) <!-- Reviewable:end -->
|
Windows doesn't really have such a limit -- each process can have as many as 16M (2^24) handles open, and there isn't a soft limit that needs to be raised. |
|
|
|
|
@bors-servo retry
|
|
|
|
|
connorimes commentedOct 13, 2015