Lunatics Windows Installer v0.40 release notes

SHHH!! We're demanding refunds, just go along with it. ^^

I have another one trying to download now, I'll be interested to see the performance of the new application.

This app works as I crunched 5 last night

ap_6.00_win_x86_SSE3_OpenCL_NV_r540.exe

AstroPulse_Kernels_r540.cl

The name of the application is v6 and call for 601 in the app_info.xml

1 hour 15 minutes approx / task

http://setiathome.berkeley.edu/results.php?userid=8612202&offset=0&show_names=0&state=0&appid=12


Michael Miles

This app works as I crunched 5 last night

ap_6.00_win_x86_SSE3_OpenCL_NV_r540.exe

AstroPulse_Kernels_r540.cl

The name of the application is v6 and call for 601 in the app_info.xml

1 hour 15 minutes approx / task

http://setiathome.berkeley.edu/results.php?userid=8612202&offset=0&show_names=0&state=0&appid=12


Michael Miles

I installed v0.40 on this pc and initially it went well, but after about 20 Cuda tasks I noticed a sharp drop in processing rate.
MSI Afterburner tells me the GPU load of only 2% with an occasional peak to 90%. I run 2 tasks at the same time on this 560Ti and the normal GPU load is 95-97%.


The result files (stderr output) do not show any information that indicates a problem.

What can I do to solve this?
____________

I went back to Lunatics_x38g_win32_cuda32.exe (only exchanged the Cuda executable and modified app_info accordingly) and it runs ok now.

Looked at most of the tasks finished today on this host and around 10-15% of these tasks took 10x the usual time. The usual time for a 2.7 AR task is 3 minutes, now some of them took 1800-3200 seconds.

I went back to Lunatics_x38g_win32_cuda32.exe (only exchanged the Cuda executable and modified app_info accordingly) and it runs ok now.

Looked at most of the tasks finished today on this host and around 10-15% of these tasks took 10x the usual time. The usual time for a 2.7 AR task is 3 minutes, now some of them took 1800-3200 seconds.

I went back to Lunatics_x38g_win32_cuda32.exe (only exchanged the Cuda executable and modified app_info accordingly) and it runs ok now.

Looked at most of the tasks finished today on this host and around 10-15% of these tasks took 10x the usual time. The usual time for a 2.7 AR task is 3 minutes, now some of them took 1800-3200 seconds.

host/task links please. we didn't change anything in that ares from v0.39 but yours is iirc the second report of sudden speed loss.

driver version?

I went back to Lunatics_x38g_win32_cuda32.exe (only exchanged the Cuda executable and modified app_info accordingly) and it runs ok now.

Looked at most of the tasks finished today on this host and around 10-15% of these tasks took 10x the usual time. The usual time for a 2.7 AR task is 3 minutes, now some of them took 1800-3200 seconds.

host/task links please. we didn't change anything in that ares from v0.39 but yours is iirc the second report of sudden speed loss.

driver version?

There's a link in the first post - host ID 5907499, driver 275.33

I'm trying to remember the history of x41g and 560Ti cards - I may need to do some digging. I think we had some early reports that some early samples of the 560Ti weren't being supplied with enough voltage to support the increased optimisation (equals workload) of x41g.

- If you run into those long runners, check the file sizes on those tasks... Could be a reappearance of those freaked out tasks, or corruption during download of some sort

Jason

- If you run into those long runners, check the file sizes on those tasks... Could be a reappearance of those freaked out tasks, or corruption during download of some sort

Jason

The mega-WUs only caused an extended delay at startup, while the coded receiver data was re-assembled using the CPU. Once the task got into its stride, the CUDA part ran at normal speed. Any other workunit corruption would have caused an error, not a slowdown - like an MD5 error, of a filesize mismatch during download, I'd have thought.

Looked through and spotted some long running shorties. There are major things to check with 560ti:
- sufficient core voltage such that it doesn't downclock (couldn't see evidence of downclock online, but possible)
- Running a solid state drive ? Make really sure its firmware is up to date... then check again. ( Yes this causes problems with Cuda apps due to broken SSDs hogging DMA, that was a real toughy to find )
- Update driver using the "clean Install" Advanced Option
- [Check temperatures] x41g pushes harder.
- running other projects with non-threadsafe Cuda apps ?
- If you run into those long runners, check the file sizes on those tasks... Could be a reappearance of those freaked out tasks, or corruption during download of some sort

Jason

1. This pc was running 24-7 in this configuration since September 25 2011. The 560Ti never showed any sign of downclocking. MSI Afterburner confirmed that nothing happened with the clockrates.
2. No SSD
3. Will update the driver and let you know the result.
4. As you can see in the Afterburner screenshot, the temperature was 60°C. Now with x38g running, the temperature is 70°C at 63% fan speed
5. No other Cuda apps were running

One other thing I should mention: prior to installing v0.40 I updated Boinc from 5.10.58 to the current 6.12.34.

If either John van Gorsel or Victor is game to try out the experimental x41u version, please PM me. I have them here ready to email (tell me your email address), or if you prefer I can find a hosting site for you to download from.