Deders
Platinum Member
- Oct 14, 2012
- 2,401
- 1
- 91
I've noticed this on some machines. I think it has something to do with how each browser is tuned to modern hardware (and not tuned for older)
Even with GPU based hardware accelerators set aside, things like the amount of SSE type registers can affect some software.
For instance with the significant boost in SSE registers that Sandybridge had over previous gens, any software developer who decides that they aren't writing code for previous gens might make more use of the SIMD's that would result in instructions queuing up on older hardware, but not on new.
Before I upgraded from Lynnfield to Skylake, Firefox was definitely laggier. I used to install Chrome on people's never upgraded P4 machines which used to make a huge difference (more so over IE than Firefox), but even now Chrome has moved on.
Even with GPU based hardware accelerators set aside, things like the amount of SSE type registers can affect some software.
For instance with the significant boost in SSE registers that Sandybridge had over previous gens, any software developer who decides that they aren't writing code for previous gens might make more use of the SIMD's that would result in instructions queuing up on older hardware, but not on new.
Before I upgraded from Lynnfield to Skylake, Firefox was definitely laggier. I used to install Chrome on people's never upgraded P4 machines which used to make a huge difference (more so over IE than Firefox), but even now Chrome has moved on.