4 ms·

> Thanks for the bug report, but I can't reproduce. According to the built-in memory profiler, Servo uses 39 MB of explicit allocations to load google.com, whic

by idobai 10y ago

> Thanks for the bug report, but I can't reproduce. According to the built-in memory profiler, Servo uses 39 MB of explicit allocations to load google.com, which is well in line with other browsers even without a whole lot of optimization for memory use. If you say so, I'll check out a new version and try it again. I've tried it a few weeks ago on linux. > A large amount of CPU usage during initial pageload, on the other hand, is a feature, not a bug. Using more resources lets us get the page loaded faster, which not only shows you the page faster but also typically reduces power consumption since we can get the CPU into an idle state. Large CPU usage slows down other apps - that's one reason why I use ff instead of chrome. 8GB RAM seems too few nowadays... > Manual memory management isn't about some broad notion of "resource consumption": it's about having low-level control of resources, which can not only reduce memory usage but also eliminate pauses. I think it's very unlikely that the JavaScript garbage collector could be made thread-safe without regressing performance (which is what you presumably mean by "just use a GC"). I was pointing to the promise that it shouldn't leak while it seems to be doing it seriously. > Just to name the first features that come to mind: Rust has a module system and hygienic macros, which are syntactic features not in C++. Rust comes with a standard library that includes networking, which isn't in C++. I don't really like Rust's module system but +1 for the hygienic macros. > Those "tweaks" are in fact likely to be slowing down your browser. Have you heard about experimental features like pipelining and prefetch? Or content restrictors like uBlock and disconnect? Or session+history limits? When I reset my ff settings(due to ff profile problems) the vanilla ff takes at least 2x as much time to load the same page. If these "tweaks" wouldn't present - I wouldn't be a happy ff user.

pcwalton 10y ago
> Large CPU usage slows down other apps - that's one reason why I use ff instead of chrome. The idea that apps should intentionally throttle their CPU usage to avoid "slowing down other apps" at the expense of performance is nonsensical. Apps should use all the resources in the machine to get the job done faster and go to sleep faster. The kernel, not userland apps, is responsible for multiplexing the system resources: that's literally its job, and only it is in a position to do so properly. > I was pointing to the promise that it shouldn't leak while it seems to be doing it seriously. Nothing you've cited has been evidence of a leak. Adding a global garbage collector would do nothing to reduce the (non-)"leaks" you observe. > Have you heard about experimental features like pipelining and prefetch? Enabling those via about:config tweaks and addons slows down your browser. Session and history limits do not affect your browser performance.
- idobai 10y ago
  > The idea that apps should intentionally throttle their CPU usage to avoid "slowing down other apps" at the expense of performance is nonsensical. Apps should use all the resources in the machine to get the job done faster and go to sleep faster. The kernel, not userland apps, is responsible for multiplexing the system resources: that's literally its job, and only it is in a position to do so properly. Did you knew that there are apps running - like IDEs, servers, games etc which requires a large amount of resources? If you run another resource hungry app it might affect your first app's runtime which would end up frozing both. Have you ever used resource hungry apps? > Nothing you've cited has been evidence of a leak. Adding a global garbage collector would do nothing to reduce the (non-)"leaks" you observe. 600MB RAM for nothing is leak. Denial is futile. > Enabling those via about:config tweaks and addons slows down your browser. Session and history limits do not affect your browser performance. 1. It seems like you don't have experience with browsers. Go and try them out instead of denying everything. Do you know what is prefetch at all? Or at least pipelining(cheat: https://en.wikipedia.org/wiki/HTTP_pipelining https://en.wikipedia.org/wiki/HTTP_pipelining)? 2. Session and history limits DOES affect browser performance at long runtime. If you limit these, your browser will consume less RAM(+ it's easier to find in small history) and if another app wants to use its resources the os will put the memory on the swap then it will come back faster.

by idobai 10y ago

pcwalton 10y ago

> Large CPU usage slows down other apps - that's one reason why I use ff instead of chrome. The idea that apps should intentionally throttle their CPU usage to avoid "slowing down other apps" at the expense of performance is nonsensical. Apps should use all the resources in the machine to get the job done faster and go to sleep faster. The kernel, not userland apps, is responsible for multiplexing the system resources: that's literally its job, and only it is in a position to do so properly. > I was pointing to the promise that it shouldn't leak while it seems to be doing it seriously. Nothing you've cited has been evidence of a leak. Adding a global garbage collector would do nothing to reduce the (non-)"leaks" you observe. > Have you heard about experimental features like pipelining and prefetch? Enabling those via about:config tweaks and addons slows down your browser. Session and history limits do not affect your browser performance.

idobai 10y ago
> The idea that apps should intentionally throttle their CPU usage to avoid "slowing down other apps" at the expense of performance is nonsensical. Apps should use all the resources in the machine to get the job done faster and go to sleep faster. The kernel, not userland apps, is responsible for multiplexing the system resources: that's literally its job, and only it is in a position to do so properly. Did you knew that there are apps running - like IDEs, servers, games etc which requires a large amount of resources? If you run another resource hungry app it might affect your first app's runtime which would end up frozing both. Have you ever used resource hungry apps? > Nothing you've cited has been evidence of a leak. Adding a global garbage collector would do nothing to reduce the (non-)"leaks" you observe. 600MB RAM for nothing is leak. Denial is futile. > Enabling those via about:config tweaks and addons slows down your browser. Session and history limits do not affect your browser performance. 1. It seems like you don't have experience with browsers. Go and try them out instead of denying everything. Do you know what is prefetch at all? Or at least pipelining(cheat: https://en.wikipedia.org/wiki/HTTP_pipelining https://en.wikipedia.org/wiki/HTTP_pipelining)? 2. Session and history limits DOES affect browser performance at long runtime. If you limit these, your browser will consume less RAM(+ it's easier to find in small history) and if another app wants to use its resources the os will put the memory on the swap then it will come back faster.