> Are there any such recommendated specs for an "ideal" valgrind running > machine? Assuming this machine will only run valgrind and nothing else.
Although it runs multithreaded programs (obviously), Valgrind itself is single threaded. This means it can only make use of one core (really, one hardware thread) per process. Hence a machine with lots of slow cores will be at a relative disadvantage to one with a few fast cores. Having a decent-sized last-level cache probably is a good thing too. That said, YMMV; you need to measure your own workload and draw your own conclusions. V's internals are complex; there are many paths that are optimised and many that aren't, because they don't seem important. It may also be that having a faster processor doesn't help much (because your-app-on-V is memory bound), or that having a processor with a larger last-level cache doesn't help much (because your-app-on-V fits well enough in a smaller LLC). I should point out too, that over the years V has acquired a bunch of machinery for collecting performance data for various aspects of its internals, which is sometimes useful for diagnosing performance problems. You could post some of that data, although that would inevitably mean publically exposing some details of your presumably proprietary application. Other things to bear in mind are: * use the latest release * probably the best-tuned port is for x86_64-linux; that may or may not be faster than ports for other targets * make sure that your test cases do a decent amount of work per process-start. I've seen cases where a test suite starts thousands of processes and does only a very short test in each process. This puts V at a severe disadvantage because it spends most of its time repeatedly instrumenting the same code over and over again, and relatively little time running that instrumented code. J _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
