Forum > Discussion Forum

AstroPulse v7 performance illustration

<< < (2/3) > >>

Mike:

--- Quote from: Richard Haselgrove on 24 Aug 2014, 06:04:17 am ---
--- Quote from: Raistmer on 24 Aug 2014, 05:54:25 am ---
Will it free core when single instance runing?


--- End quote ---

Not unless we go all the way up to 1.00 - which I think is possibly (but open to discussion) overkill for general users. And if we do that, we consume a whole thread of CPU for each and every AP in progress - which, again, I think is a bit over the top. Not every user is a hardcore optimizer! (and those who are, can look after themselves, as always).

--- End quote ---

You mean like Mark and Juan ?

Richard Haselgrove:
LOL.

We'll teach them software yet!

Raistmer:
Then I would suggest -cpu_lock option instead as enabled by default in aistub and installer.
I'll test this suggestion in next few days. Maybe this should be default mode for stock too, will see.

Richard Haselgrove:

--- Quote from: Raistmer on 24 Aug 2014, 06:11:53 am ---Then I would suggest -cpu_lock option instead as enabled by default in aistub and installer.
I'll test this suggestion in next few days. Maybe this should be default mode for stock too, will see.

--- End quote ---

Makes sense. Like you, I want to make minimal changes possible for the interim v0.42 installer, so there'll be no behavioural change in v0.42c for people to get used to, but I think it's a discussion worth having between v0.42 and v0.43

Raistmer:
And here is update for initial graph with -cpu_lock data added.

As one can see the usage of -cpu_lock on GPU app leads to some increase of elapsed time for CPU apps 9and reported CPU time remains the same). Maybe it reflects inability of OS to move GPU app process between cores so it either leave core idle for some time or starts to move CPU app processes more actively that increases overhead. This decrease performance on CPU side.
But there is much more noticeable effect on GPU side. Now elapsed times for GPU tasks have much lass deviation and grouped toward their bottom boundary (especially for low-blanked tasks). This lead to big increase in productivity on GPU side that will offset some loss of performance on CPU side. Also, CPU side performance can be affected non-BOINC activity on this host so more data set required to make sure if CPU performance has some decrease indeed. But increase in GPU performance is obvious. Compare blue and greed dots. Number of dots is comparable so data sets can be directly compared.

After little more data collection in -cpu_lock regime I plan to show how freeing CPU core (w/o -cpu_lock) will affect host performance.

EDIT: more data added, graph updated. Now in "1 core idle" mode for collection new data.

Navigation

[0] Message Index

[#] Next page

[*] Previous page