Lunatics Windows Installer v0.40 release notes

So just to confirm, when I get to this, which may be a week from now, i7-2 will be fastest with SSE3 correct? Or should I try SSSE4.x as it's a i7-2?

Hmm, definitely weird. Well we'll find out one way or another. With those things eliminated, if after updating driver you still get weirdness, we will get you testing x41u. Can't very well push out an updated release next week if there is some unknown latent problem lurking.

Jason

v6.00 with r540 should validate against v6.01 with r555.

The difference between them is not in task validation, but another part of the code which helps to keep the project running smoothly, with sensible runtime estimates.

That bit affects us all, so it would be a great help if people could ensure that they are running at least r555 as in the installer, not any earlier beta version - as Michael is now doing. Thank you.

OK I know next to nothing about it, but shouldn't my new notebook use AVX with the new AP app?

Seems it didn't or I'm not reading it correctly ;)

http://setiathome.berkeley.edu/result.php?resultid=2371596165

OK I know next to nothing about it, but shouldn't my new notebook use AVX with the new AP app?

Seems it didn't or I'm not reading it correctly ;)

http://setiathome.berkeley.edu/result.php?resultid=2371596165

OK I know next to nothing about it, but shouldn't my new notebook use AVX with the new AP app?

Seems it didn't or I'm not reading it correctly ;)

http://setiathome.berkeley.edu/result.php?resultid=2371596165

You'll have to ask Jason how AVX usage is flagged in the task output. You meet all the criteria we know about - running the r557 app, second-generation i7, Windows 7 with SP1.

But as we said a couple of days ago, we just run the delivery service: we're not responsible for the contents, I'm afraid.

Edit: if you copy wisdom.dat from your project folder to the desktop, and open it with notepad, you'll see what codelets were used.

Claggy

Yes wondered about that file, and it does contain some AVX stuff.

Also no problem to test the x41u on the Q9660/GTX560Ti. This pc is only used for testing and running Boinc. I will send a PM to Richard.

Victor is also reporting issues, & has giving up testing in a snot.

Right now I have no idea what's causing either of your issues. Will look at some of your results...
____________
"It is not the strongest of the species that survives, nor the most intelligent that survives. It is the one that is the most adaptable to change."
Charles Darwin

Victor is also reporting issues, & has giving up testing in a snot.

Right now I have no idea what's causing either of your issues. Will look at some of your results...

Do you have a link to x38G Jason?

The pc is now running x41u_cuda32, 1 task at a time. When all 4 cores are used, there are dropouts where the GPU load is close to 0 for about 20-30 seconds. The progress bar in Boinc is then still moving, but only at around 0.001% per second.
With 1 core free, the GPU load slightly increases, but there are no more dropouts.

I checked both the Linux pc's running x41g for the difference when 1 thread or core is left free:
Q9650 + GTX260 running Seti Cuda and 2xSeti AK_v8 + 1xLHC T4T on the CPU:
"Top" shows a 6-8% cpu utilization from x41g
With 3x Seti and 1 x LHC T4T, the cpu load drops to 3-6% and Cuda tasks run at around half the speed

i7-920 + GTX570 448 running Seti Cuda (3 tasks) and 6xWCG + 1xLHC T4T on the CPU
"Top" shows a 4-9% cpu load for each of the three instances of x41g
There is no difference whith 7x WCG + 1xLHC T4T but the WCG application may not be as demanding as the Seti AK_v8. Tomorrow I will try the same with 7xAK_v8

[edit] the first tasks on the i7 at "full load" took about 15% longer than with one thread free. The difference is smaller then with the Q9650 but there is a difference.

Figured it out I think/Hope

Some time back, ~x38g, I had detected many programs including OpenCL & CPU apps throttling the Cuda programs which was killing the threads, so I raised the app prioties to normal so they'd stay alive.

Unfortunately, in doing so, I was bombarded by demands to put it back to below normal, which I did for x41 series.

Please try to use something like either Fred'd efMer prioroty tool, or Process Lasso to jack up the Cuda process priorities. I'll consider making the default priorities configurable in the near future. Both x41g & x41u should operate normally when not being throttled by other programs running at higher priorities.

This will slightly delay next release, but hopefully not too much

Thanks for the help tracking this down. I'll think harder next time before reversing design decisions based on angry dudes comments.

Jason
____________
"It is not the strongest of the species that survives, nor the most intelligent that survives. It is the one that is the most adaptable to change."
Charles Darwin

Right now I have no idea what's causing either of your issues. Will look at some of your results...

Thanks,
Can you jack up the cuda process priorities (with one of the tools mentioned) & compare ?

BTW: for some reason I'm having trouble getting to your images.

Jason
____________
"It is not the strongest of the species that survives, nor the most intelligent that survives. It is the one that is the most adaptable to change."
Charles Darwin