More work available for Linux than for Windows?

ulenz
ulenz
Joined: 22 Jan 05
Posts: 27
Credit: 17897764
RAC: 0
Topic 195187

While running Vista 64-bit BOINC-manager has often told me that there is no work available for einstein@home.

On the same PC there are lots of workunits for einstein@home available while running the computer using Ubuntu-Linux 64 bit.
Is there a special reason for that difference in getting workunits?

Intel Q9300 Quadcore, 2500 Mhz, 4096 MB RAM, GeForce 9800 GT, Vista Ultimate 64-bit, Ubuntu 10.10 64 bit

Gary Roberts
Gary Roberts
Moderator
Joined: 9 Feb 05
Posts: 5887
Credit: 119478355257
RAC: 25998971

More work available for Linux than for Windows?

Quote:
Is there a special reason for that difference in getting workunits?


Yes, it's called 'luck' :-).

All tasks at E@H can be done by any of the supported platforms. There is no distinction between different OS's. If a task is available, it will be given to you, irrespective of whether you are running Windows or Linux.

Actually, I'm not seeing any difficulty in getting tasks at the moment. Are you talking about the S5GC1 tasks or the ABP2 tasks?

I've just had a look at your host in its two different forms. There seems to be no problems running Linux but you have lots of client errors when running Vista. I looked at a couple and the error message goes like this

[13:36:38][5452][INFO ] Starting data processing...
[13:36:38][5452][ERROR] Error acquiring "real" CUDA device!
------> The acquired device is a "Device Emulation (CPU)"
[13:36:38][5452][ERROR] Demodulation failed (error: 1014)!
13:36:38 (5452): called boinc_finish

So it looks like you get a lot of tasks but many are immediately erroring out.

I don't have any CUDA devices so I have zero experience. Is it possible that Vista's eye candy is consuming too much graphics memory or perhaps you don't have the best driver? Someone else who knows more about this will need to advise you.

Cheers,
Gary.

ulenz
ulenz
Joined: 22 Jan 05
Posts: 27
Credit: 17897764
RAC: 0

Thanks for your answer,

Thanks for your answer, Gary!
Most features of the "Aero"-Desktop are disabled when running Vista 64 bit. While changing between the two os each day I could observe these differences in downloading workunits. I have taken a look at this problem for the last two weeks.

Probably there is a problem inside BOINC for Windows 64 bit. First I have to log in as root to get the cuda-device running. Hereafter I log in into a second account as a regular user without privileges as root. This is due to the driver architecture of Vista 64 bit in contrary to the 32 bit versions of Windows.
But this feature doesn't explain, why BOINC for Windows has downloaded much less workunits than BOINC for Linux.

Intel Q9300 Quadcore, 2500 Mhz, 4096 MB RAM, GeForce 9800 GT, Vista Ultimate 64-bit, Ubuntu 10.10 64 bit

Gary Roberts
Gary Roberts
Moderator
Joined: 9 Feb 05
Posts: 5887
Credit: 119478355257
RAC: 25998971

RE: But this feature

Message 98554 in response to message 98553

Quote:
But this feature doesn't explain, why BOINC for Windows has downloaded much less workunits than BOINC for Linux.


I didn't look far enough to see that your Linux incarnation is also trashing tasks - but not nearly as many as with Windows. You actually have quite a few pages of tasks for each version of your machine so it doesn't really seem like too much of a shortage :-).

As errored tasks get returned, the scheduler will reduce your ability to get further tasks until you start to return successful ones. Is it possible that this is what you are seeing with Windows? I could imagine that if you downloaded 16 tasks and trashed them all, your daily allocation would be reduced from 32 to 16 (which you already have had) so the scheduler would refuse to send any more until a new day rolled around.

You would see this in the messages tab as it would tell you that you have exceeded your daily quota of X tasks (where X is some number significantly less than 32) - so it should be reasonably obvious if that was happening. However, since you are trashing many more Windows tasks than Linux tasks, I wonder if this is why you are being denied Windows tasks?

This is all rather academic as your highest priority should be to work out why either platform is causing tasks to be trashed. As I don't use CUDA, I have no experience to offer, I'm sorry.

Cheers,
Gary.

Mike Hewson
Mike Hewson
Moderator
Joined: 1 Dec 05
Posts: 6594
Credit: 338954748
RAC: 434804

FWIW : I use CUDA on a

FWIW : I use CUDA on a Windows 7 64 bit machine without difficulty, including screen saver operation.

Cheers, Mike.

I have made this letter longer than usual because I lack the time to make it shorter ...

... and my other CPU is a Ryzen 5950X :-) Blaise Pascal

ulenz
ulenz
Joined: 22 Jan 05
Posts: 27
Credit: 17897764
RAC: 0

Einstein@home for Windows 64

Einstein@home for Windows 64 bit reports that the output files for workunits are absent.
I have done a fresh installation of the actual BOINC-software and the latest nvidia-drivers for my gpu. What can I do now? Any idea?

Intel Q9300 Quadcore, 2500 Mhz, 4096 MB RAM, GeForce 9800 GT, Vista Ultimate 64-bit, Ubuntu 10.10 64 bit

Gundolf Jahn
Gundolf Jahn
Joined: 1 Mar 05
Posts: 1079
Credit: 341280
RAC: 0

There are two messages in the

Message 98557 in response to message 98556

There are two messages in the stderr output of those tasks. Number one is only informational but sounds suspicious to me:Eine der Dateien in der Registrierungsdatenbank musste ?in Protokoll oder eine Sicherungskopie wiederhergestellt werden. Die Wiederherstellung war erfolgreich. (0x3f6) - exit code 1014 (0x3f6)
The second one denotes the real problem:

[16:59:34][4576][ERROR] Error acquiring "real" CUDA device!
------> The acquired device is a "Device Emulation (CPU)"
[16:59:34][4576][ERROR] Demodulation failed (error: 1014)!


Gruß,
Gundolf
[edit]I just saw that Gary already mentioned those errors on 30 Jun 2010. Perhaps you should go to your Einstein@Home preferences and set "Use NVIDIA GPU" to "no".[/edit]

Computer sind nicht alles im Leben. (Kleiner Scherz)

ulenz
ulenz
Joined: 22 Jan 05
Posts: 27
Credit: 17897764
RAC: 0

Running Windows XP 32 bit SP2

Running Windows XP 32 bit SP2 results in the same errors. The output file is not present. But it doesn't seem to be a hardware problem, because Cuda on Ubuntu Linux seems to work correctly.

Intel Q9300 Quadcore, 2500 Mhz, 4096 MB RAM, GeForce 9800 GT, Vista Ultimate 64-bit, Ubuntu 10.10 64 bit

Bernd Machenschalk
Bernd Machenschalk
Moderator
Administrator
Joined: 15 Oct 04
Posts: 4349
Credit: 253396068
RAC: 37402

For the Techs (maybe s.o. can

For the Techs (maybe s.o. can translate):

The underlying problem is that the BOINC Core Client (which uses the 'CUDA Driver API') sees the CUDA device differently than the Application (which uses NVidias cuFFT and the 'CUDA Runtime API'). This is a known problem with CUDA on Windows. NVidia doesn't seem to have a solution (yet), and we don't either. We currently don't even have time to further investigate this. The only thing we could do so far is to detect this situation and stop the Application before any computing time is wasted, which results in the message 'The acquired device is a "Device Emulation (CPU)"'. Continuing using the Emulation Device (which is the only one visible to the 'CUDA Runtime API') would stop the App after really long time.

BM

BM

Ver Greeneyes
Ver Greeneyes
Joined: 26 Mar 09
Posts: 140
Credit: 9562235
RAC: 0

So the BOINC client locates a

Message 98560 in response to message 98559

So the BOINC client locates a functional CUDA device, but the Einstein@Home application can't see it? Does this only apply to a specific subset of cards?

ulenz
ulenz
Joined: 22 Jan 05
Posts: 27
Credit: 17897764
RAC: 0

Here are the datas for my own

Message 98561 in response to message 98560

Here are the datas for my own gpu:
"Sparkle SX98GT1024D3G-VP, 1024 MB GDDR3 1800 Mhz/256bit, Taktfrequenz 550Mhz, Shader-Takt 1375 Mhz, Shader-Modell. 4.0"

Intel Q9300 Quadcore, 2500 Mhz, 4096 MB RAM, GeForce 9800 GT, Vista Ultimate 64-bit, Ubuntu 10.10 64 bit

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.