
Originally Posted by
ChrisJefferson
I'm one of the developers of Minion, although I know very little about the phoronix test suite!
Compiling Minion in it's default build is a major undertaking -- memory usage can pass 700MB. On my dual core macbook, compiling takes around 59 minutes.
Even worse, if your compiler decides to compile multiple files at the same time, then memory usage grows to your number of cores, which is, I suspect, what is happening to you!
There are ways of compiling Minion which lead to a much more manageable compile, while leading to a reasonable (~30%) reduction in run-time. The simplest is to add ' -DQUICK ' to the call to cmake. I'd be happy to discuss this, and any other details about Minion and designed a good testsuite based around it. In particular, there are some Minion files which particularly stress the memory manager, while others spend most of the their time just doing CPU work in user-space.