Welcome to MilkyWay@home

The increase in the calculation time at Win 10 (x64)


Advanced search

Message boards : Number crunching : The increase in the calculation time at Win 10 (x64)
Message board moderation

To post messages, you must log in.

AuthorMessage
kararom

Send message
Joined: 9 Jan 09
Posts: 19
Credit: 1,009,149,134
RAC: 0
1 billion credit badge13 year member badge
Message 63903 - Posted: 8 Sep 2015, 8:24:38 UTC

After the transition to Windows 10 (x64) and install the latest video card driver calculation time jobs increased significantly.

There are 2 video AMD 280x (not Crossfire)

The calculation is carried out in two streams on each graphics card.

Task v 1.02 (opencl_amd_ati) are considered on the processor for about 95 seconds and then they are on the same video card about 50 seconds (this is evident from the Windows Task Manager and TechPowerUp GPU-Z)

I do not know what to do about it

Please help me.

P. S.: Sorry for my English
ID: 63903 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profilemikey
Avatar

Send message
Joined: 8 May 09
Posts: 2870
Credit: 465,819,808
RAC: 66,871
300 million credit badge13 year member badgeextraordinary contributions badge
Message 63904 - Posted: 8 Sep 2015, 10:40:30 UTC - in response to Message 63903.  

After the transition to Windows 10 (x64) and install the latest video card driver calculation time jobs increased significantly.

There are 2 video AMD 280x (not Crossfire)

The calculation is carried out in two streams on each graphics card.

Task v 1.02 (opencl_amd_ati) are considered on the processor for about 95 seconds and then they are on the same video card about 50 seconds (this is evident from the Windows Task Manager and TechPowerUp GPU-Z)

I do not know what to do about it

Please help me.

P. S.: Sorry for my English


New drivers are not ALWAYS better for crunching as we are NOT their main customers. Other than that I have no idea.
ID: 63904 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
kararom

Send message
Joined: 9 Jan 09
Posts: 19
Credit: 1,009,149,134
RAC: 0
1 billion credit badge13 year member badge
Message 63909 - Posted: 9 Sep 2015, 8:10:21 UTC

Yes, the driver v. 15.7.1 does not work properly.

Install the drivers AMD-Catalyst-14-9-win7-win8.1-64Bit-dd-ccc-whql (v. 08.00.0916) - everything works well.

Thanks for the tip!
ID: 63909 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profilemikey
Avatar

Send message
Joined: 8 May 09
Posts: 2870
Credit: 465,819,808
RAC: 66,871
300 million credit badge13 year member badgeextraordinary contributions badge
Message 63910 - Posted: 9 Sep 2015, 11:31:55 UTC - in response to Message 63909.  

Yes, the driver v. 15.7.1 does not work properly.

Install the drivers AMD-Catalyst-14-9-win7-win8.1-64Bit-dd-ccc-whql (v. 08.00.0916) - everything works well.

Thanks for the tip!


No problem. Now just don't forget to make it so Win10 doesn't auto install the new ones again.
ID: 63910 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
kararom

Send message
Joined: 9 Jan 09
Posts: 19
Credit: 1,009,149,134
RAC: 0
1 billion credit badge13 year member badge
Message 63912 - Posted: 9 Sep 2015, 16:13:59 UTC

OK!
ID: 63912 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfileMumak
Avatar

Send message
Joined: 8 Apr 13
Posts: 89
Credit: 517,085,245
RAC: 0
500 million credit badge9 year member badgeextraordinary contributions badge
Message 63958 - Posted: 1 Oct 2015, 9:37:43 UTC

I see a similar issue after upgrading to Win10. One of my machine (R9 280X) spends ~30 secs initial time on CPU, another one (2xHD 7950) ~50 secs. This is a huge overhead against previous results on Win7 (1-3 seconds CPU time per task).
Checking results of different users running Win10 and similar cards shows that many others are affected, but I found some that are not and running Catalyst 15.9. Not sure what's the difference and how to fix this.
I have tried the latest driver 15.9.1 Beta released yesterday, but it's still the same. However I haven't been able to downgrade the AMD GPU drivers to some older version, it still retains the latest driver installed. Automatic driver update is disabled in Win10.
ID: 63958 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Abinars

Send message
Joined: 30 Jul 14
Posts: 1
Credit: 149,561,756
RAC: 0
100 million credit badge7 year member badge
Message 64025 - Posted: 23 Oct 2015, 5:12:01 UTC

It is not just win 10 I had the same problem with win 7 and the stated driver.
Went from 24 sec. to 1 min. per unit It is strange because I had installed driver v. 15.7.1 a week ago and it was just today that it changed.
Went back to 14.12 worked fine
ID: 64025 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profilemikey
Avatar

Send message
Joined: 8 May 09
Posts: 2870
Credit: 465,819,808
RAC: 66,871
300 million credit badge13 year member badgeextraordinary contributions badge
Message 64029 - Posted: 23 Oct 2015, 9:33:09 UTC - in response to Message 63958.  

I see a similar issue after upgrading to Win10. One of my machine (R9 280X) spends ~30 secs initial time on CPU, another one (2xHD 7950) ~50 secs. This is a huge overhead against previous results on Win7 (1-3 seconds CPU time per task).
Checking results of different users running Win10 and similar cards shows that many others are affected, but I found some that are not and running Catalyst 15.9. Not sure what's the difference and how to fix this.
I have tried the latest driver 15.9.1 Beta released yesterday, but it's still the same. However I haven't been able to downgrade the AMD GPU drivers to some older version, it still retains the latest driver installed. Automatic driver update is disabled in Win10.


Are you leaving a cpu core free just for the gpu to use? If not try it and see if that helps.
ID: 64029 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfileMumak
Avatar

Send message
Joined: 8 Apr 13
Posts: 89
Credit: 517,085,245
RAC: 0
500 million credit badge9 year member badgeextraordinary contributions badge
Message 64039 - Posted: 25 Oct 2015, 19:51:05 UTC

I tried, but it didn't help.
I have been running MW@H on the same machines before summer and there were no such issues. After summer I returned back and see this behavior.
ID: 64039 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profilemikey
Avatar

Send message
Joined: 8 May 09
Posts: 2870
Credit: 465,819,808
RAC: 66,871
300 million credit badge13 year member badgeextraordinary contributions badge
Message 64042 - Posted: 26 Oct 2015, 11:48:51 UTC - in response to Message 64039.  

I tried, but it didn't help.
I have been running MW@H on the same machines before summer and there were no such issues. After summer I returned back and see this behavior.


I don't know then.
ID: 64042 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfileMumak
Avatar

Send message
Joined: 8 Apr 13
Posts: 89
Credit: 517,085,245
RAC: 0
500 million credit badge9 year member badgeextraordinary contributions badge
Message 64096 - Posted: 13 Nov 2015, 15:57:08 UTC

Not sure whether it's because of upgrading Win10 to TH2 (1511) or Catalyst to 15.11 Beta, but it works now as before, so no extensive CPU usage anymore.
ID: 64096 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profilemikey
Avatar

Send message
Joined: 8 May 09
Posts: 2870
Credit: 465,819,808
RAC: 66,871
300 million credit badge13 year member badgeextraordinary contributions badge
Message 64097 - Posted: 14 Nov 2015, 14:28:04 UTC - in response to Message 64096.  

Not sure whether it's because of upgrading Win10 to TH2 (1511) or Catalyst to 15.11 Beta, but it works now as before, so no extensive CPU usage anymore.


That's good!!
ID: 64097 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfileMumak
Avatar

Send message
Joined: 8 Apr 13
Posts: 89
Credit: 517,085,245
RAC: 0
500 million credit badge9 year member badgeextraordinary contributions badge
Message 64098 - Posted: 14 Nov 2015, 15:25:32 UTC

FWIW - I checked logs and it seems that it was the upgrade to Win10 TH2 (1511) that fixed things.
ID: 64098 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profilemikey
Avatar

Send message
Joined: 8 May 09
Posts: 2870
Credit: 465,819,808
RAC: 66,871
300 million credit badge13 year member badgeextraordinary contributions badge
Message 64099 - Posted: 15 Nov 2015, 12:26:50 UTC - in response to Message 64098.  

FWIW - I checked logs and it seems that it was the upgrade to Win10 TH2 (1511) that fixed things.


It went smoothly on my own Win10 machine too, mine is JUST a cruncher but still no problems.
ID: 64099 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfileMumak
Avatar

Send message
Joined: 8 Apr 13
Posts: 89
Credit: 517,085,245
RAC: 0
500 million credit badge9 year member badgeextraordinary contributions badge
Message 64113 - Posted: 17 Nov 2015, 16:49:57 UTC
Last modified: 17 Nov 2015, 16:50:25 UTC

Spoke too early - was running well for a few days, but now it's again consuming a lot of CPU time at the beginning.
No idea why is that...
ID: 64113 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfileMumak
Avatar

Send message
Joined: 8 Apr 13
Posts: 89
Credit: 517,085,245
RAC: 0
500 million credit badge9 year member badgeextraordinary contributions badge
Message 64122 - Posted: 24 Nov 2015, 17:39:25 UTC

Now after installing the Crimson drivers it's back to normal.
Wondering how long it will stay...
ID: 64122 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
disturber

Send message
Joined: 11 Jan 15
Posts: 8
Credit: 75,884,093
RAC: 0
50 million credit badge7 year member badge
Message 64131 - Posted: 29 Nov 2015, 15:15:07 UTC

I had a big problem keeping Windows 10 from installing new drivers. Even after uninstalling and deleting the new driver from the hidden windows store repository, it still downloaded it and re-installed it a few hours later. This happened after I checked all the check boxes disabling driver install with instructions I found on the windows help page.

So my solution was to disable the Driver Install service using the administrative program. The 13.251 driver has now been updated for a week after this happened. For my 7970 card, any of the newer drivers slow it down. This applies not only to this project but for Einstaein@Home as well.
ID: 64131 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Message boards : Number crunching : The increase in the calculation time at Win 10 (x64)

©2022 Astroinformatics Group