A very frequent checkpointing set in the boinc user preference will slow down the application (even by 50% more). New application version will fix this.

GDF

A very frequent checkpointing set in the boinc user preference will slow down the application (even by 50% more). New application version will fix this.

GDF

Fixed by version 6.34 for Linux.

GDF

Hi

Where can we modify this (the frequency of the checkpoints) in the boinc user preference? I haven't found this option :/

I trie the new application (2.30) on windows and it seems to be similar as the 2.29 one

Thank you for your involvement and your presence for this project :)

Hi

Where can we modify this (the frequency of the checkpoints) in the boinc user preference? I haven't found this option :/

I trie the new application (2.30) on windows and it seems to be similar as the 2.29 one

Thank you for your involvement and your presence for this project :)

It's in Advanced, Preferences, Disk and Memory usage.
"Write to disk at most every" xx "seconds"

Mine is set to 60 seconds.
How often is "frequent checkpointing" that causes the slowdown?

---

Down with the Kredit Kops!!!

Ah, thanks UBT - NaRyan, mine is set to 60 sec too

I beleive 60 is the default. I had mine bumped up to 300s/5m or 600s/10m depending on my venue. Been that way for a year or more. I've noticed no ill effects with using this time with any project, except to note, if you turn off computer or boinc when any app restarts you loose up to that much time depending on when the last checkpoint was, whereas with 60s you loose only 1 minute, if app checkpoints per preferences that is. But shutdowns happen not that much so it is a good compromise to save on disk writes and/or speed up app processing.

---

GDF ?

I've noticed an increase of time to process work between 6.28 and 6.29. 6.29 is taking another 10,000s/2.75h or so. We still get exact same credit so I'm guessing something has slowed down the app processing, but it appears across all 3 of my hosts so I doubt it is something I have changed as any changes on my end are usually not across all 3. Is this the checkpoint issue ?

I've noticed an increase of time to process work between 6.28 and 6.29. 6.29 is taking another 10,000s/2.75h or so. We still get exact same credit so I'm guessing something has slowed down the app processing, but it appears across all 3 of my hosts so I doubt it is something I have changed as any changes on my end are usually not across all 3. Is this the checkpoint issue ?

I've seen the same increase in processing time on Linux with apps 6.33 & 6.34,
8800GT ~45k -> ~57k seconds
8800GS ~49k -> ~78k seconds

Yeah noticing the same slow down here on Linux also.
It's only been going for 6 hours, however normaly 6 hours is 50% complete, at the moment it's at 40% complete.

At this rate it's going to workout taking nearly as long as the Windows version does :(

Also since the new windows app was released, all workunits have started to crash once again for me on windows :(

---

Down with the Kredit Kops!!!

Hi, my first work unit with the new App is done, and I would like to have the old one back, please...

Instead of 48.000 seconds I need 75.000 seconds to finish one unit now. This is 27.000 seconds more! Nothing except the app changed on my side, system wasn't updated or rebooted.

How come that there is such a dramatic increase?

http://www.ps3grid.net/results.php?hostid=6998

Was that one maybe a special unit which is supposed to take that long?

Hi, my first work unit with the new App is done, and I would like to have the old one back, please...

Would be nice, as an increase from 11 hours 45 minutes, to just over 15 hours (for me), ain't nice from an app that was supposed to have sped things up (with checkpointing)

And I still cannot get a workunit to run for more than a few seconds on my Win XP x64 system, since the new windows app was released.....

All fail with the same error: 3 (0x3)
"<core_client_version>6.3.8</core_client_version>
<![CDATA[
<message>
The system cannot find the path specified. (0x3) - exit code 3 (0x3)
</message>
<stderr_txt>
# Device 0: "GeForce 8800 GTX"; Clock rate: 1350000 kilohertz
MDIO ERROR: cannot open file "restart.coor"
Cuda error: Kernel [kick_drift_kernel] failed in file 'step.cu' in line 48 : the launch timed out and was terminated.
Assertion failed: 0, file step.cu, line 48

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

</stderr_txt>
]]>"

---

Down with the Kredit Kops!!!

Clearly, the problem was not just checkpointing. Even my machine is slower. I know at least a couple of things that we have changed that could slow it down, but if it is the extra debugging code, you need to stand it for a little while.
New application is coming up.

gdf

Hi, my first work unit with the new App is done, and I would like to have the old one back, please...

Would be nice, as an increase from 11 hours 45 minutes, to just over 15 hours (for me), ain't nice from an app that was supposed to have sped things up (with checkpointing)

And I still cannot get a workunit to run for more than a few seconds on my Win XP x64 system, since the new windows app was released.....

All fail with the same error: 3 (0x3)
"<core_client_version>6.3.8</core_client_version>
<![CDATA[
<message>
The system cannot find the path specified. (0x3) - exit code 3 (0x3)
</message>
<stderr_txt>
# Device 0: "GeForce 8800 GTX"; Clock rate: 1350000 kilohertz
MDIO ERROR: cannot open file "restart.coor"
Cuda error: Kernel [kick_drift_kernel] failed in file 'step.cu' in line 48 : the launch timed out and was terminated.
Assertion failed: 0, file step.cu, line 48

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

</stderr_txt>
]]>"

i get the same error.
i use drivers 177.35 with boinc 6.3.8 on win xp 32b.

Good news, the slowness problem is not in the debugging code but a flag left on while debugging which should not be on.
Application 6.36 for Linux will fix it. Coming up.

gdf

Very good, I'm really looking forward to that release :-D

Though it seems not all crunchers where effected by the slowness of 6.34, one user from our team reports that he crunched 2 WUs with 6.34 at the same speed as with the older apps...

Very good, I'm really looking forward to that release :-D

Though it seems not all crunchers where effected by the slowness of 6.34, one user from our team reports that he crunched 2 WUs with 6.34 at the same speed as with the older apps...

Application 6.37 out. I expect that once we upload also the new Windows application, Linux and Windows will have the same speed. It may be convenient to abort new wu which you have already if they start with the old application.

gdf

Application 6.37 out. I expect that once we upload also the new Windows application, Linux and Windows will have the same speed. It may be convenient to abort new wu which you have already if they start with the old application.

gdf

The computer that has the 8800GTX and is running Linux is now crashing with in a few seconds.

Always with the error

"<core_client_version>6.3.8</core_client_version>
<![CDATA[
<message>
process exited with code 1 (0x1, -255)
</message>
<stderr_txt>
# Using CUDA device 0
# Device 0: "GeForce 8800 GTX"
# Clock rate: 1350000 kilohertz
Cuda error: Kernel [reduce4_kernel] failed in file 'reduction.cu' in line 123 : the launch timed out and was terminated.

</stderr_txt>
]]>"

That's using the 173.14.12 drivers (installed using Envy), I have them installed on the system that has the 2 8800GT's in it and it is working fine (on 1 card for the moment)

I see that driver 177.67 is listed on the Nvidia get cuda page for linux x64, should I try them instead?

---

Down with the Kredit Kops!!!

Application 6.37 out.

6.37 is still slow for me :(

http://www.ps3grid.net/show_user.php?userid=5044

6.25 -> 48.000s
6.34 -> 74.500s
6.37 -> 64.500s

Where has the speed gone?

The computer of my team mate:

6.33 -> 46.767s - 48.000s
6.34 -> 49.000s
no Result for 6.37 yet

So I wonder how his 6.25 would have looked like, and also why he is 25.000 seconds faster on 6.34 with the only difference being 16 shaders and 125MHz shader clock more...

Application 6.37 out.

6.37 is still slow for me :(

Weird 6.37 is back to normal speed for me.

6.34 took around 54,434.09 Seconds
6.37 took 42,579.39 Seconds

---

Down with the Kredit Kops!!!