I've seen my runtimes go from 20 minutes to 1.5 hours with the new 1.3 version. Running Win 7 x64, two 5870s. Mucked with which core, app_info.xml, etc and still the same performance

You crunched around 50 WUs with V1.3 at your standard crunch time.

It started to go wrong 0040 UTC today. Did you change anything on the installation last night - driver, Win Update, new utilities, any new software?? If you did that may have corrupted something.

Run with no app_info, see what happens

Try a quick check that memory boards and cards have not worked slightly loose - unlikely as that would cause straight errors, but its a quick elimination.

I'd then try a reset first, and reload project files.

If still hassles, do a Project attatch/detatch

If that doesnt do it, I'd then suspect the AMD Driver had become corrupt (clean it totally with Driver sweeper and registry check before reloading fresh driver).

Post again if still running slow after that lot.

Regards
Zy

Thanks. I'm not sure what happened. I detached/attached and everything seems to be running at the right rate.

Thanks. I'm not sure what happened. I detached/attached and everything seems to be running at the right rate.

Never mind. It started out fast, but is now taking 1.5 hours. I've also reinstalled the ATI drivers.

Did you clean out the old drivers with Driver Sweeper and run a registry check ?

Regards
Zy

Went back a version in the drivers to 11.11 still the same other projects like collatz and milkyway are taking the normal amount of time. It's just Moo on my two ATIs that is running real slow. I didn't start changing stuff until today, so I have no clue what the problem is.

Bit of a loss as to what to go for to be honest - anyone any ideas fire away :)

Due to other projects running fine, Hardware is ok, BOINC is ok, driver is ok. You've detatched/attatched, so project files are ok. The application is fine - run thousands of times by now on 58XX cards, and in any case you've crunched it 50 times successfully, so its not the app.

The only thing I can thing of is there is lurking a file from V1.2 still hanging around causing a clash, or the registry is messed up.

The last shot in my bag, is do another atatch/detatch - and immediately afterwards, before running anything, do a registry clean. Virus check maybe, and make sure the project directory is an exception on the virus checker on standard running ..... but thats clutching at straws frankly.

Regards
Zy

I was making some changes and tried boinc v7, but have gone back to 6.x.x

Now I don't seem to be able to do core selection the same way - the list looks a but confusing in the prefs - all I want is to pick #3 core.

Two hour run time is too long considering I was at 6-7 minutes last week.

Edit: think I found the info and settings I needed running benchmarking

I was making some changes and tried boinc v7, but have gone back to 6.x.x

Now I don't seem to be able to do core selection the same way - the list looks a but confusing in the prefs - all I want is to pick #3 core.

Two hour run time is too long considering I was at 6-7 minutes last week.

Edit: think I found the info and settings I needed running benchmarking

Let us know what the fix was so that if it's happening elsewhere folks can work with what you learned and save some time.

Bit of a loss as to what to go for to be honest - anyone any ideas fire away :)

Due to other projects running fine, Hardware is ok, BOINC is ok, driver is ok. You've detatched/attatched, so project files are ok. The application is fine - run thousands of times by now on 58XX cards, and in any case you've crunched it 50 times successfully, so its not the app.

The only thing I can thing of is there is lurking a file from V1.2 still hanging around causing a clash, or the registry is messed up.

The last shot in my bag, is do another atatch/detatch - and immediately afterwards, before running anything, do a registry clean. Virus check maybe, and make sure the project directory is an exception on the virus checker on standard running ..... but thats clutching at straws frankly.

Regards
Zy

He is still running version 11.11 of the drivers, aren't they still not good for crunching and shouldn't he be at 11.9 or less right now.

I was making some changes and tried boinc v7, but have gone back to 6.x.x

Now I don't seem to be able to do core selection the same way - the list looks a but confusing in the prefs - all I want is to pick #3 core.

Two hour run time is too long considering I was at 6-7 minutes last week.

Edit: think I found the info and settings I needed running benchmarking

I thought the core picking was only available in the brand new 7 series? Which of course some projects don't support yet as they are still in testing.

.... He is still running version 11.11 of the drivers, aren't they still not good for crunching and shouldn't he be at 11.9 or less right now.

As a general proposition, yup, best stay away from the later ones. However its not absolute, they will run, I am running 11.12 on my main box. He is getting massive slowdown - its huge - that cant be the driver, too big for that (assuming the driver install is a good one). Hence thoughts over maybe a bit left from V1.2 somewhere.

Your second point may have mileage in it though ... its a good thought .... the new options should be used with care. If they have been played with, I'd reset them all to -1 (the default) and see what happens on the WU. Same goes for the .ini file, the default setting of 9 for CPU doesnt work for everyone (I reset mine back to V1.2 level of 4).

Its worth a shot as you indicate .... would be interesting to know if its was that in the end, because this one is real, real, unusual, something wacky is going on.

Regards
Zy

was having problems last week as well.went from about 54 minutes on the huge wu,to over 4 hours.the activity on the gpu would bounce around like a pin ball machine,then go to zero for 30 minutes or more,then start bouncing again.was told fragmented work units.tried going to boinc 7.0.8,no improvement.added the app info file,no help either.i even put in the pre release from amd for the 12.1 driver for the gpu,still no help.oh,btw,7.0.8 caused more problems than it solved.pretty much everything began failing...http internal server errors,no uploads or down loads.finally got fed up and dumped everything,reinstalled 6.12.34,dumped the app info file,now im getting the small work units and everything is working like it should...as far as i know.so from what i read ,the huge wu,are where the problem lies,something about they are very fragmented,and are causing lots of headaches.
so while im here,which is why i started writing this in the first place,what pourous does v 1.3 serve any way.am seeing no change in times,takes about 13-15 minutes to run what ever size wu there sending me,on a 6770.dont really know if thats slow or fast.

He is still running version 11.11 of the drivers, aren't they still not good for crunching and shouldn't he be at 11.9 or less right now.

I went back to 11.9. Still the same Moo times.

Well I tried this.

Uninstall ATI drivers.
Detach all boinc projects.
Unistall boinc.
Delete C:/ProgramData/Boinc
Install ATI drivers.
Install Boinc.
Attach to Moo.

Still same. I have 13 million till my 100 million mark. I guess I'm limping into home :-(

I know this will sound wacky .... but hey we are at that stage .... go try a memory test on main system memory, an extended one not just a quickie. I know its unlikely, but different apps use memory in different ways. I have seen it before that an app will run, but another will not, turned out to be a memory stick had gone bad.

I am starting to go more and more towards hardware somewhere, albeit I know a Logic shows it cant be. However you've changed just about every bit of software there is, and no go - apart from a Windows reinstall, and I guess there is a far fetched logic that says try a windows reinstall ..... but its a hell of a lot of work for something so unlikely.

Give the memory test a whirl, doesnt take much, and at least that would be eliminated if nothing else. (The Windows built in memory checker is not bad, run it as a first check, but make sure you retest as well with a good third party test software as well)

Regards
Zy

Looking at the ATI GPUs I use, I see the runtimes of WUs, using the 1.03 client, seem to have increased by between 13% and 29% on the pre-Xmas bonus and other issued.

The upside is the CPU usage is the same, and the credit given is @7065, but RAC falling slowly.

My ATI drivers are still at 1.4.1332 or 11.3

I was making some changes and tried boinc v7, but have gone back to 6.x.x

Now I don't seem to be able to do core selection the same way - the list looks a but confusing in the prefs - all I want is to pick #3 core.

Two hour run time is too long considering I was at 6-7 minutes last week.

Edit: think I found the info and settings I needed running benchmarking

Let us know what the fix was so that if it's happening elsewhere folks can work with what you learned and save some time.

Sorry - bad of me.

1: Stopped boinc.
2: Went to the project directory and ran the "dnetc518-win32-x8x.exe" program.
3: Ran the benchmarking option (client -> benchmark -> all cores, all projects)
4: Noticed that the core numbers had descriptions net to them and for me, #3 matched one of those in the pull down list.

Different computers have different core descriptions. So there is a small amount of attention required.

Anyway - running that box to get its RAC to #1 in the project for fun. Should be some time after I pass the 100M milestone. Then it might go back to earning money for me.

Looks like a return of an old long crunch time on the huge WUs.

The quad with my single HD5850 was originally completing a huge WU in 38.xx minutes. That was after my initial project start when the WUs were crunched in 1 hour 20 minutes. The correction for this was to raise the "processor -usage priority from 4 to 9" in the dnetc-gpu-1.2 file, and then the shorter times applied.

Since these fragmented units came about the crunch time per WU seemed to rise to 41 to 42.xx minutes, but credit given also rose marginally.

Last night I crunched a bunch of Wus in 1 hour 20 minutes and see the dnetc-gpu-1.3 file has the processor priority at 9, so I cannot do anything.

Is there a solution, Teemu?

Ever since 1.03 I do not seem to get a mix of units anymore. I seem to only get normal size. My faster card ran the large ones well and my slower one would grab normal to small. I'd like to see the mix again. I've made no changes on my end.