On Wednesday, 6 December 2017 20:13:50 GMT Alan McKinnon wrote: > On 06/12/2017 21:10, Mick wrote: > > I discovered that building Chromium with gcc-6.4.0 is taking an > > inordinately> > > longer time on a laptop with 1st gen i7 and 4G of RAM, e.g.: [snip...]
> Pure gut feel and intuition and nothing else leads me to look in two places: > > You use -march=native on the i7 so I assume the same on the Core2? Those > are rather different processors, and google is fond of optimizing deeply > for specific cases (common to all browsers I think). You'd have to ask a > chromium hacker but I'd say the odds are good there are serious > optimizations for i7 that stress your compiler out muchly. Yes, I run -march=native on both. > Add to that your i7 is RAM-constrained so you compensate with swap, > which is easily 50,000 times slower with sucky latency. Yes, it's ridiculously slow! :-( > When you use a > disk as RAM, performance tanks. Well, usually it causes a cascade effect > and stuff blows up, but if it completes it will have done so slowly. > > If you at all can, shove lots more RAM in that i7. These days RAM is > cheap and it's always by first performance tweak, then SSD. I know that compiling in RAM would be done in a fraction of the time. The thing is, this is a 8 year old laptop and I am resisting throwing good money after bad. I had a quick look a few months ago and good quality memory will cost me around £60. With the battery shot and the keyboard on its way out, I'd rather put the money towards more memory for a newer PC, sometime in the next year. ;-) -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
