I give you freely my GPU time, and the cost of the electricity to run it, because I believe in GPUGRID. What do you do in return? Send me WUs that make my PC unusable.

Unusable? How about 10 seconds to react to a click on the Start button? How about 18 seconds to open Task Manager? How about 11 seconds to go from one browser tab to another?

I have eight CPU processors, Windows 7 and six Megs of RAM, more than enough to give instantaneous response to any of these actions, under normal circumstances.

Problem? NATHAN WUs. My log of all WUs downloaded these past 30 days shows, for non-benHP NATHANs:

 69 received, of which:
 17 ran with no problems,
 5 ran but with performance problems,
 7 gave ‘error while computing’ and
 40 were aborted by me because they were killing my PC.

I can tell you the WU names of all the 69 received, by category.

A 25% success rate should be a concern for you. It certainly is for me! I have to nurse PC-crippling WUs. In the last hour I’ve aborted six. I signed up for hands-off background processing. That is not what’s happening!

I do hope you will work with me to get to the bottom on this misery…

Tom

---

Just curious if you have ever given thought to only crunching these projects when you are not using your computer/ GPU? By the nature of all of these tasks they are there to use up any excess system power you have, but if your need for performance suddenly spikes by suddenly requiring more than you were in processing power for your own use then its only natural for the program to wait until that extra power can be alocated, which can be on the order of several tens of seconds.

While I do not have any projects that I myself administer, I find it funny when people expect their machines to react like they have no extra load put on them when crunching.

Think about it this way if you are employed to be someone's assistant, you can respond to all their requests instantaneously if they haven't assigned you extra projects and you are only focusing on meeting your bosses demands. But if while you are their assistant you are told you need to also sort and file all of the documents in a few hundred person organization, and see your to your bosses needs, when suddenly when your boss asks you to do something, you may want to finishing filing what you were then see to your bosses needs. But, if you were told to only file when your boss was not in the office that would never happen.

So you need to decide are you hunting credits, or are you doing it for the good of the science. If you are doing it for the science, then aborting all these extra work units is detrimental to the science, and you should just set your machine to only crunch when you are not using it.

Just curious if you have ever given thought to only crunching these projects when you are not using your computer/ GPU? By the nature of all of these tasks they are there to use up any excess system power you have
,...
and you should just set your machine to only crunch when you are not using it.

I agree that GPUGRID , as well as other projects using CPU only, is designed for using part or all of the idle time of the system. So it normally sholud let the system responsive if well configured.

But I think that tomba's problem is not with the WUs themselves , a lot of crunchers have no problem with that, except when some WUs are not well designed..

According to me, the cause is either :

- a configuration problem (GPUGRID and/or system)
- a hardware problem (GPU and/or motherboard)
- an inadapted combination of CPU/OS/GPU ...

This seems very fuzzy, but the problem seems not WU related...

@tomba : Please give a COMPLETE description of your system in terms of hardware brands, bios and drivers versions, RAM size and speed etc...
I know we already discussed about your problem in another thread but I'm sure every one here is willing to help solve this "mystery"...

Regards

---

Lubuntu 16.04.1 LTS x64

The only problem I get is laggy graphics when running the long runs. Which is why I'm gonna stick to the normal runs.

disable "Use GPU while computer is in use", have you even tried?

I have had similar "problems" but this is the way I see the issue: NATHAN has gotten some of his work units SO EFFICIENT that they use up practically ALL of gpu's resources. This is a GOOD THING for the project IMO! There should be no idle resources in a well-coded application. The only work units that have given me "problems" are the ones running at 99% gpu utilization.

If you want to use your system for other tasks then you will have to give up some of those resources, plain and simple (at least I think it's simple).

---

XtremeSystems.org - #1 Team in GPUGrid

I give you freely my GPU time, and the cost of the electricity to run it, because I believe in GPUGRID. What do you do in return? Send me WUs that make my PC unusable...

Call of the dogs!! I found the solution. I did not know that, after unchecking "Use GPU while computer is in use" in BOINC / Tools / Computing Preferences / Processor Usage, I had to activate this preference in BOINC / Activity by checking "Use GPU based on preferences".

Now when I wiggle the mouse in BOINC / Tasks, the GPUGRID WU immediately gives "Waiting to run". Perfect!

Apologies to everyone, Tom

---

Just curious if you have ever given thought to only crunching these projects when you are not using your computer/ GPU? By the nature of all of these tasks they are there to use up any excess system power you have
,...
and you should just set your machine to only crunch when you are not using it.

I agree that GPUGRID , as well as other projects using CPU only, is designed for using part or all of the idle time of the system. So it normally sholud let the system responsive if well configured.

But I think that tomba's problem is not with the WUs themselves , a lot of crunchers have no problem with that, except when some WUs are not well designed..

According to me, the cause is either :

- a configuration problem (GPUGRID and/or system)
- a hardware problem (GPU and/or motherboard)
- an inadapted combination of CPU/OS/GPU ...

This seems very fuzzy, but the problem seems not WU related...

@tomba : Please give a COMPLETE description of your system in terms of hardware brands, bios and drivers versions, RAM size and speed etc...
I know we already discussed about your problem in another thread but I'm sure every one here is willing to help solve this "mystery"...

Regards

Hey. No need write so long because real broblem is here:

I have eight CPU processors, Windows 7 and six Megs of RAM, more than enough to give instantaneous response to any of these actions, under normal circumstances.

6 megabytes of memory + 8 processor cores is not a good combination. Update the machine for at least 6 GB of memory, so we can think about the problem again. Now, the problem is far too small amount of memory.

That was a typo!

---

FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

That was a typo!

I assume you're referencing my "six megs". Right! Six GIGS, of course...

Sorry.

Tom

---

Now when I wiggle the mouse in BOINC / Tasks, the GPUGRID WU immediately gives "Waiting to run". Perfect!

Not quite perfect... When a WU resumes it backs-off a few percentage points of processing so it's repeating what it's already done.

I guess it's resuming at the last checkpoint. I've looked and looked for the parameter that lets me specify the checkpoint period but I can't find it!

Any ideas?

Tom

---

Now when I wiggle the mouse in BOINC / Tasks, the GPUGRID WU immediately gives "Waiting to run". Perfect!

I think this is not a normal behaviour if crunching has to be suspended every time you move the mouse ?!?!?!?

I never experienced this situation with any GPU !

---

Lubuntu 16.04.1 LTS x64

I think this is not a normal behaviour if crunching has to be suspended every time you move the mouse ?!?!?!?!

It is normal if you have a modest GPU - GTX 460 - and many WUs kill your PC performance and you set the GPU to not run when you are using your PC.

---

Hi, The best solution is to have a unique GPU for display and the other GPUs for BOINC, if your requirements allow.

The GPU of the screen is excluded from use BOINC (cc_config.xml) and no problems of delays etc ...

I'm using a GT 620 for the screen (pass a GTS450 coming soon) and a GTX 590 for BOINC without delay and maximum performance. Greetings.

Hi, The best solution is to have a unique GPU for display and the other GPUs for BOINC.

Lucky to have two GPUs!!

---

Hi, The best solution is to have a unique GPU for display and the other GPUs for BOINC.

Lucky to have two GPUs!!

Hello: A Zotac GeForce GTS 450 ECO Edition with 192 CudaCores no extra power needed is about 75 € and performs perfectly for almost everything (except applications or games very severe).

In my opinion, the problem should be the usage of GDDR memory. When I run this program, the loading of GDDR is almost 100%. But the loading of system memory is very low. These code may claim too large variables on the video card waiting to progressing. I don't know how sources code looks like but this is what i thought.

by the way, the thinking of distributed computing is the same as run on a supercomputer. These program should not be design to run on a powerful computer but an old one ( like the generation of one or two years ago ). Or you will lost a lot of volunteers while more and more people have the same feeling like tomba. Meanwhile, that will be a bad news to you.

In my opinion, the problem should be the usage of GDDR memory. When I run this program, the loading of GDDR is almost 100%. But the loading of system memory is very low. These code may claim too large variables on the video card waiting to progressing. I don't know how sources code looks like but this is what i thought.

by the way, the thinking of distributed computing is the same as run on a supercomputer. These program should not be design to run on a powerful computer but an old one ( like the generation of one or two years ago ). Or you will lost a lot of volunteers while more and more people have the same feeling like tomba. Meanwhile, that will be a bad news to you.

the 400 series cards are already 2-2.5 years old and still work on GPUGrid. GPUGrid still works on the 200 series which is in fact 3-4 years old, so what is your point?

---

XtremeSystems.org - #1 Team in GPUGrid

In my opinion, the problem should be the usage of GDDR memory. When I run this program, the loading of GDDR is almost 100%. But the loading of system memory is very low. These code may claim too large variables on the video card waiting to progressing. I don't know how sources code looks like but this is what i thought.

by the way, the thinking of distributed computing is the same as run on a supercomputer. These program should not be design to run on a powerful computer but an old one ( like the generation of one or two years ago ). Or you will lost a lot of volunteers while more and more people have the same feeling like tomba. Meanwhile, that will be a bad news to you.

the 400 series cards are already 2-2.5 years old and still work on GPUGrid. GPUGrid still works on the 200 series which is in fact 3-4 years old, so what is your point?

My points is these program are not compatible to these card well. Code could be modified for volunteers. Or GPUGRID think these are not important to this project.

Don't be a barney....it is wise to do a bit of research prior to getting out the blame thrower..just a thought.

I guess it's resuming at the last checkpoint. I've looked and looked for the parameter that lets me specify the checkpoint period but I can't find it!

It's a property of the WU and is not cruncher-configurable.

MJH