I don't suffer from lag here, I have an i7 3820 and the coolest 580(temperature wise) gpu, a PNY LC 580.

I'm not a programmer, I'm a hardware guy, but it would be nice if running vlars could be optimized.

If you run the stock application then it will (eventually) select the application that gives the best throughput.


If you choose to run something that is only at the Beta stage of release- not yet close to general release- then it's up to you to select the application & then tweak it to give the best results. The information you provide back will allow those developing the applications to make the release version better. Unfortunately the documentation on what each variable is & does & what's best & not best doesn't really exist- this is still a Beta release remember.
But there are people around that can help.

I run Lunatics 0.44...

I tried 0.45, opencl and Me aren't compatible, since most of opencl seems to be cpu work, I opencl you'd think would work on the gpu like cuda does.

---

Savoir-Faire is everywhere!
The T1 Trust, T1 Class 4-4-4-4 #5550, America's First HST

I run Lunatics 0.44...

Lunatics is an installer, nothing more.
It allows you to select the applications that you want to run.

This thread is about Lunatics 0.45 which allows people to select the r3430 SoG app.
If you are having issues with the installer, this is the thread to post in.

If you are having issues with the SoG application, then the "OpenCL NV MultiBeam v8 SoG edition for Windows" is the thread to post in.

If you are having other issues, check for an existing thread on that topic. If there aren't any around, then I suggest starting one.

---

Grant
Darwin NT

Note that to test the SoG application you have to run the v0.45 Beta installer, and choose that particular application from the versions offered.

When your SoG test is complete, you can - if you wish - re-run the v0.45 installer and choose one of the CUDA applications instead. There's no need to keep two separate installers on your hard disk.

My AMD 4200 does not like this installer for CPU tasks :(

I have tried SSE2 SSE3 but all are Computation Errors. And it was fine before.

<snip>

From Jason

Ugh, that one again. Tweeted Eric & Marius a link to the other thread, just because they happened to be on my twitter feeds.

Is there any news on this front? My AMD is CPU dead now.

My AMD 4200 does not like this installer for CPU tasks :(

I have tried SSE2 SSE3 but all are Computation Errors. And it was fine before.

<snip>

From Jason

Ugh, that one again. Tweeted Eric & Marius a link to the other thread, just because they happened to be on my twitter feeds.

Is there any news on this front? My AMD is CPU dead now.

Did you try SSE version from my website ?

---

With each crime and every kindness we birth our future.

My AMD 4200 does not like this installer for CPU tasks :(

I have tried SSE2 SSE3 but all are Computation Errors. And it was fine before.

<snip>

From Jason

Ugh, that one again. Tweeted Eric & Marius a link to the other thread, just because they happened to be on my twitter feeds.

Is there any news on this front? My AMD is CPU dead now.

Saw activity before the weekend on Boinc Dev, and discussions on the other thread here as well. So I believe wheels are in motion

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

Saw activity before the weekend on Boinc Dev, and discussions on the other thread here as well. So I believe wheels are in motion

What activity/discussions are you referring to, please? I didn't think I'd made any changes to the CPU path for this test installer, except removing the MB_v7 support.

Saw activity before the weekend on Boinc Dev, and discussions on the other thread here as well. So I believe wheels are in motion

What activity/discussions are you referring to, please? I didn't think I'd made any changes to the CPU path for this test installer, except removing the MB_v7 support.

At the time of the post, I was probably incorrectly associating his 'unknown error; / CreateProcess() failed with the other one, where there was activity on the mentioned weirdness. My apologies if an unrelated issue.

[Edit:] Oddly, looking at the AMD Athlon 64 X2 spec, it says it supports SSE3, so this one would need more digging.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

My AMD 4200 does not like this installer for CPU tasks :(

I have tried SSE2 SSE3 but all are Computation Errors. And it was fine before.

<snip>

From Jason

Ugh, that one again. Tweeted Eric & Marius a link to the other thread, just because they happened to be on my twitter feeds.

Is there any news on this front? My AMD is CPU dead now.

Saw activity before the weekend on Boinc Dev, and discussions on the other thread here as well. So I believe wheels are in motion

Which makes the original question/problem all the more mysterious. The errored tasks are there for all to see, and I found Task 4939380044, which confirms it was working before.

Can we leave this until the morning, and dig into it then, please? My head is spinning after assembling six new ATI aistubs with up to 34 different different platform/version/plan_class combinations in each.

<snore/>

My AMD 4200 does not like this installer for CPU tasks :(

I have tried SSE2 SSE3 but all are Computation Errors. And it was fine before.

<snip>

From Jason

Ugh, that one again. Tweeted Eric & Marius a link to the other thread, just because they happened to be on my twitter feeds.

Is there any news on this front? My AMD is CPU dead now.

Saw activity before the weekend on Boinc Dev, and discussions on the other thread here as well. So I believe wheels are in motion

Which makes the original question/problem all the more mysterious. The errored tasks are there for all to see, and I found Task 4939380044, which confirms it was working before.

Can we leave this until the morning, and dig into it then, please? My head is spinning after assembling six new ATI aistubs with up to 34 different different platform/version/plan_class combinations in each.

<snore/>

Yep, as per edit, the chip supposedly supports SSE3, and sleeping on it sounds like a good idea.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

Managed to kill all CPU tasks after updating _GPU_app via new installer %)
http://setiathome.berkeley.edu/results.php?hostid=4517643&offset=0&show_names=0&state=6&appid=

<core_client_version>7.4.42</core_client_version>
<![CDATA[
<message>
couldn't start app: CreateProcess() failed - (unknown error)
</message>
]]>

4294967111 (0xffffff47) Unknown exit code

And now I suppose I know what this "CreateProcess() failed" means.
x86 OS and x64-only provided installer.
So, if you see such error on CPU app download x86 build from my cloud and manually revert back to proper binary:
https://cloud.mail.ru/public/3nxq/SgQBZXcM7

Well at least seems to be reproducible. permissions or damage of some sort I guess [Perhaps fftw library ?]. Time for that sleep

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

As the title says. Beta test only, try at your own risk.

I think we should dig out the old "Advanced Users only" tag for this one - I'm not sure whether it will fly or not.

This installer has been updated for NVidia only so far - DO NOT USE IT if you are currently running stock applications for ATI/AMD or intel GPUs.

This is basically the v0.44 installer (64-bit only, to start with), with the following changes....

RTFM. Sorry about that. Edit - yes, Brent Norman is running a 32-bit copy of Windows XP on that host. There's a Beta2, in both 32-bit and 64-bit formats, coming tomorrow if I can cram an atiapu selection button into the UI. That's always the toughest part.

As the title says. Beta test only, try at your own risk.

I think we should dig out the old "Advanced Users only" tag for this one - I'm not sure whether it will fly or not.

This installer has been updated for NVidia only so far - DO NOT USE IT if you are currently running stock applications for ATI/AMD or intel GPUs.

This is basically the v0.44 installer (64-bit only, to start with), with the following changes....

RTFM. Sorry about that.

That'd do it :D

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

yep, make that bolded in first post too.
At least Brent's case is closed.
He has 32-bit XP host.

Anybody got an incompatibility wizard I can use to detect a 32-bit operating system from a 32-bit application (the installer itself), to say "Hi. I'm a 64-bit application really"?

Don't use the sleep command with SoG/Lunatics 0.45, at present it causes wu's to slow down and report estimated completion times in the thousands of days, then the status will say 'Waiting to run', while other wu's get worked on, I've had nothing but trouble with this, it doesn't matter if the wu is a guppi or not, I've aborted at least 5 wu's that would just sit there and do nothing.

. . May I ask how much memory you have?

. . I am running 0.45 Beta with -use_sleep turned on on this rig. I have not experienced any such problems but it does cause the GPU utilisation to become sporadic and drop quite low. My average was about 30%. For non Guppi tasks this was overcome by running multiple instances which behaved nicely and well mannered. With three WUs running the GPU is now achieving almost 100% usage and runtimes are only about 75% greater (20 mins running singly, 36 running triples).

. . Sadly Guppis are as cantankerous as ever, they take about 50 to 52 mins with sleep on, but instead of working concurrently as triples they seem to want to run as singles playing tag with the GPU and work load did not budge, staying at about 30%, and runtimes went from 52 mins to 3 hours and 20 mins. Killed my hopes and expectations that they would take about 1 hour 30 mins or less. It seems there is no way to run Guppis on an Nvidia card without wasting large amounts of resources.

Then I think I'd rather not do Guppi wu's on My gpu, I'd rather abort any that I find on My 580 gpu. I think I might go back to Lunatics 0.44.

. . Here, here!

. . Guppis are fine as CPU tasks but on Nvidia cards they are total brats.

I'd rather abort any that I find on My 580 gpu.

Better not to crunch at all than to abort.

. . So what is it about aborting WUs that gets so many people upset. Does it release the Kraken or something?

. . Better to abort a WU than to have it stuff up a machine and prevent it from working on other tasks.