On Thu, Sep 30, 2010 at 8:00 PM, Johannes Kimmel <johannes.kim...@gmx.de> wrote: > On 09/30/2010 12:58 PM, Mark David Dumlao wrote: >> >> Heya, >> I noticed that my firefox-bin is a lot smaller in memory footprint >> compared to ordinary gentoo-compiled firefox. >> >> Does anyone know what compiler flags upstream applies to their >> firefox? I turned off the custom-optimization USE on mine assuming >> that it would follow upstream optimizations, but maybe it doesn't. >> > > I thought firefox-bin is a 32-bit binary. If you are using a 64-bit gentoo > it is likely you self compiled version is a lot bigger.
That's right, firefox-bin is a 32bit binary, but I didn't expect the Virt size to have a nearly 3x difference (855MB vs 355MB) when loading the same tabs and running the same profile, or the Res size to have nearly double (200MB vs 130MB). Is this a speed vs size tradeoff thing? Because I noticed that my compiled firefox is doing something like 10-30 points higher in the google v8 benchmark than firefox-bin. But that's relatively a small improvement, I think my system would do better overall with the giant memory use reduction. Or is there an issue with having both firefoxes using the same profile dirs (not at the same time though). -- This email is: [ ] actionable [ ] fyi [ ] social Response needed: [ ] yes [ ] up to you [ ] no Time-sensitive: [ ] immediate [ ] soon [ ] none
