Christian Weisgerber wrote:
My best guess at this time is that lzo2 somehow manages to induce
crazy cache thrashing on some CPU models.
Ideas and explanations welcome
Try running single command that is different on different machines under
valgrind (callgrind) on these machines and see that at least number of
instructions
executed is the same.
Lzo2 documentation says that there are a lot of algorithms implemented.
It might be choosing the algorithm based on the CPU and the choice it's
making might be bad.
Yuri
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
