Yea DHEP ran much cooler than SETI, Asteroids or LHC on my i7 4930k (Ivybridge E).
So we're meant to run PG & DHEP in parallel?
Probably not. Edit: Well, not on the same machine, anyway. Hence my "conflict of interest".
I wonder what sort of code DHEP's application is; including, why it runs cooler.
Is it accessing RAM a lot? In that case it would not go well together with PG's LLR based application, which itself accesses RAM extensively if there is not sufficient cache. (And even if the CPU has enough cache for one or a few LLR processes, if there is an additional load which wildly jumps around in RAM, that load may cause the CPU to evict hot data of the LLR processes from the caches, I am afraid.)
Or is DHEP simply just branch-heavy code, instead of data intensive? In that case, a certain amount of DHEP could perhaps be put onto those HyperThreads which are of little to no use anyway when LLR is doing its thing.
So far it runs cool and seems to not require much memory.
If it doesn't allocate much memory, then perhaps it also doesn't access memory very intensively.
Of course, instead of idly wondering, I could as well simply test it with the very same method with which I tested for LLR throughput in the past (back then without any concurrent loads). But not today anymore.
@Assimilator1, as
noted by
@crashtech, PG's LLR based projects love Haswell and later, and conversely don't shine on Ivy Bridge and former. Hence, the Ivy Bridge-E should have more of a momentum at DHEP.
(Though I for one will probably run neither during the Formula Boinc sprint.)