|
|
|
|
|
by srean
4228 days ago
|
|
To give a counterpoint, I frequently get into trouble with Linux 3.12.6. If I open more than a few tabs (70 say, with FF I can do an order of magnitude more) in Chrome it maxes out on memory to the point of the system becoming useless. Funnily enough it actually maxes out on swap space even though there is RAM available and then starts thrashing like crazy. Setting swappiness alleviates this somewhat but not entirely. Its a box with 1 GB ram + 1 GB swap. Not big by current standards, but has more than plenty RAM in my opinion if it werent for the tendency to write bloatware these days. Yeah I could get some more RAM, but this box is a good testbed for software with a leaner streak, bloat does not excite me as much, sorry. Funnily enough this seems to offend a whole lot of people, as if I owe it to them to have more RAM on my m/c. It is probably worth it just for that amusement. Definitely interested in giving *BSD a shot. The thing that has stopped me so far is the difficulty in sharing data between them. EDIT @DanBC > 70 tabs is not normal and 700 is just, well, weird. So I have been told :) Firefox manages it well enough though, I would assume Dillo would too. Dont want to hijack the thread with why I abuse tabs so, but I still contend that 1 GB is enough if the code is tight. 1 GB is a huge freaking load of memory if you think about it. |
|
I'd be interested in what happens if you run 700 Dillo instances?