Puzzled, once more

Message boards : Number crunching : Puzzled, once more
Message board moderation

To post messages, you must log in.

AuthorMessage
Phil Burden

Send message
Joined: 26 Oct 00
Posts: 264
Credit: 22,303,899
RAC: 0
United Kingdom
Message 1550021 - Posted: 30 Jul 2014, 17:51:58 UTC

It appears, from the little I've observed, that my ATI Radeon 6950 does less crunching when there is no monitor attached to it, does that make sense? Must admit, it doesn't to me ;-)

P.
ID: 1550021 · Report as offensive
Profile HAL9000
Volunteer tester
Avatar

Send message
Joined: 11 Sep 99
Posts: 6534
Credit: 196,805,888
RAC: 57
United States
Message 1550071 - Posted: 30 Jul 2014, 19:27:56 UTC - in response to Message 1550021.  
Last modified: 30 Jul 2014, 19:28:16 UTC

It appears, from the little I've observed, that my ATI Radeon 6950 does less crunching when there is no monitor attached to it, does that make sense? Must admit, it doesn't to me ;-)

P.

If the monitor goes to sleep, from the Windows power save settings, the GPU slows down to its lower clock rates. With a "no monitor" condition I would expect the same behavior.
If a monitor is connect but powered off this does not happen.
SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[
ID: 1550071 · Report as offensive
Phil Burden

Send message
Joined: 26 Oct 00
Posts: 264
Credit: 22,303,899
RAC: 0
United Kingdom
Message 1550097 - Posted: 30 Jul 2014, 20:14:43 UTC - in response to Message 1550071.  

It appears, from the little I've observed, that my ATI Radeon 6950 does less crunching when there is no monitor attached to it, does that make sense? Must admit, it doesn't to me ;-)

P.

If the monitor goes to sleep, from the Windows power save settings, the GPU slows down to its lower clock rates. With a "no monitor" condition I would expect the same behavior.
If a monitor is connect but powered off this does not happen.


Once again I thank you ;-)

P.
ID: 1550097 · Report as offensive
Profile FalconFly
Avatar

Send message
Joined: 5 Oct 99
Posts: 394
Credit: 18,053,892
RAC: 0
Germany
Message 1550177 - Posted: 30 Jul 2014, 22:07:54 UTC - in response to Message 1550097.  

Weird, I would be surprised to see any influence on the GPU clocks of a loaded GPU (i.e. by BOINC).

So far I never noted any difference even in non-monitor equipped multi-GPU setups under 24/7 load with BOINC.
ID: 1550177 · Report as offensive
Phil Burden

Send message
Joined: 26 Oct 00
Posts: 264
Credit: 22,303,899
RAC: 0
United Kingdom
Message 1550386 - Posted: 31 Jul 2014, 7:45:06 UTC - in response to Message 1550177.  
Last modified: 31 Jul 2014, 7:45:26 UTC

Weird, I would be surprised to see any influence on the GPU clocks of a loaded GPU (i.e. by BOINC).

So far I never noted any difference even in non-monitor equipped multi-GPU setups under 24/7 load with BOINC.



Well, in my case, the number of wu's processed by the card definitely dropped, from around 90 a day to 50 a day, for the 2 days, which meant my RAC also dropped.
;-( One other weird thing happened as well, I switched the monitor to the onboard Intel gpu, which Boinc then "saw" and promptly gave me another 100 wu's. Now I've switched back to the Radeon, the iGPU isn't seen by Boinc any more.
ID: 1550386 · Report as offensive
Profile HAL9000
Volunteer tester
Avatar

Send message
Joined: 11 Sep 99
Posts: 6534
Credit: 196,805,888
RAC: 57
United States
Message 1550471 - Posted: 31 Jul 2014, 13:25:34 UTC - in response to Message 1550386.  
Last modified: 31 Jul 2014, 13:28:27 UTC

Weird, I would be surprised to see any influence on the GPU clocks of a loaded GPU (i.e. by BOINC).

So far I never noted any difference even in non-monitor equipped multi-GPU setups under 24/7 load with BOINC.



Well, in my case, the number of wu's processed by the card definitely dropped, from around 90 a day to 50 a day, for the 2 days, which meant my RAC also dropped.
;-( One other weird thing happened as well, I switched the monitor to the onboard Intel gpu, which Boinc then "saw" and promptly gave me another 100 wu's. Now I've switched back to the Radeon, the iGPU isn't seen by Boinc any more.

If you want BOINC to "see" the iGPU all the time here is a way to do it.
http://www.hal6000.com/seti/manual_display_detect.htm

Once this has been set & BOINC sees the iGPU you can then change the display settings back to non extended. The iGPU still be seen until you restart BOINC.
SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[
ID: 1550471 · Report as offensive
Profile FalconFly
Avatar

Send message
Joined: 5 Oct 99
Posts: 394
Credit: 18,053,892
RAC: 0
Germany
Message 1550554 - Posted: 31 Jul 2014, 16:44:11 UTC - in response to Message 1550471.  
Last modified: 31 Jul 2014, 16:49:32 UTC

Well I'll be damned....

HAL9000 is absolutely right.

I just ran GPU-Z logging during the period of having the monitor shutdown (HD7970 on Win7).

The result :
GPU load consistently dropped from 99% to 87% despite still running 2 GPU tasks.

PS.
So far I thought the only source of significant loss of crunch performance came from forgetting that BOINC by default also installs and sets its screensaver, sucking performance while running (if one forgot about that detail after installing it).
ID: 1550554 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14650
Credit: 200,643,578
RAC: 874
United Kingdom
Message 1550591 - Posted: 31 Jul 2014, 18:18:08 UTC - in response to Message 1550554.  

PS.
So far I thought the only source of significant loss of crunch performance came from forgetting that BOINC by default also installs and sets its screensaver, sucking performance while running (if one forgot about that detail after installing it).

And if one forgot to deselect the screensaver option during installation.
ID: 1550591 · Report as offensive
Profile HAL9000
Volunteer tester
Avatar

Send message
Joined: 11 Sep 99
Posts: 6534
Credit: 196,805,888
RAC: 57
United States
Message 1550617 - Posted: 31 Jul 2014, 19:07:05 UTC - in response to Message 1550554.  

Well I'll be damned....

HAL9000 is absolutely right.

I just ran GPU-Z logging during the period of having the monitor shutdown (HD7970 on Win7).

The result :
GPU load consistently dropped from 99% to 87% despite still running 2 GPU tasks.

PS.
So far I thought the only source of significant loss of crunch performance came from forgetting that BOINC by default also installs and sets its screensaver, sucking performance while running (if one forgot about that detail after installing it).

On my notebook the GPU clock drops from 750MHz to 150MHz. The GPU load stays about the same for me, but processing is slowed to 20% of normal speed.
SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[
ID: 1550617 · Report as offensive
Profile FalconFly
Avatar

Send message
Joined: 5 Oct 99
Posts: 394
Credit: 18,053,892
RAC: 0
Germany
Message 1550627 - Posted: 31 Jul 2014, 19:54:58 UTC - in response to Message 1550617.  
Last modified: 31 Jul 2014, 19:56:15 UTC

On my setup (HD7970), the GPU and VRAM clocks weren't reduced - but the GPU utilization dropped some ~12% plus some VRAM was being freed (while 2 GPU tasks running).

Hard to tell how much performace got lost that way but I can imagine it must have been a chunk.
ID: 1550627 · Report as offensive

Message boards : Number crunching : Puzzled, once more


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.