Nate, are you saying it is queuing only one workload at a time? Before we were having a bit of the opposite problem where on startup of a new project it would queue double the necessary work units. It would eventually settle to a reasonable queue depth of work units over time after it burned through the first ones. I hope the new adjustments didn't swing it the other way.
[/quote]

I set the config to send 4 WUs per core. It had been set at 10. I can set it back if necessary...

I dug a little deeper. If I understand this correctly, some older boinc clients don't report the host's resources (i.e. number of cores). In that case, the project will treat the host as having 1 core and will send only 4 WUs.

@NATE1 - I think it's something 'different' with this projects server setup. I always run with a 1 day cache, so am unfamiliar with the 0 day cache method. Presumably other projects only send one WU in this case?

@Eric - I think *all* client versions correctly reported the number of cores. I guess your server is set up to always send 4 WUs minimum per core - In NATE1's case he's asking for 1 seconds work (I think) and getting more than one WU which is probably wrong. It's like when attaching to the project, when it inits it should receive just one WU. Might be worth enquiring on the BOINC messages boards or via the mailing list.

Al.

Nate/Eric - FYI, I just saw this this over at the BOINC forums:

http://boinc.berkeley.edu/dev/forum_thread.php?id=6848#39718

Al.

My computer can run 8 at a time. Right now it is only running 4 and getting message "this computer has reached limit on tasks in progress". I was at 6.10.56 and moved up to latest for linux 6.10.58 and it did not help.

From message before sounds like it was going to be 4 per core and looks like that may not be the case.

I set the config to send 4 WUs per core. It had been set at 10. I can set it back if necessary...

Looks like it may be 4 per computer. My 2 cores get 4 and my 4 core get 4. My 8 cores gets 4 so only running at 50% on that one unless I run another project.

I would also really like to be able to cache some work units and right now only my computers with 2 cores have a 2 WU cache.

Thanks,
Glenn

Well, it looks like we may have over-adjusted and some work queues were getting short. I put the depths back to the original values and we will look into finer adjustments later.

Well, it looks like we may have over-adjusted and some work queues were getting short. I put the depths back to the original values and we will look into finer adjustments later.

They have 10 WU now. Thanks.

if you get Mr. W over at bam/bonic stats to get the project in the sign up for projects, if your ready, you could have maybe 8000 new user in less that a week
plus I lazy and it would be an easy way to attach my other 6 computers.

Thanks Nate. Good to know. We have a couple more issues to work out and then I think we will be ready to do that.

@ Nate,

How did you install BOINC? Did you install from Ubuntu repositories using apt-get or did you use the Berkeley installer from the BOINC site?

If you used the Berkeley installer then you can upgrade to BOINC 6.12.34. I did and it works fine. You might run into trouble with a few missing shared libs but if you install those you'll be OK. It worked for me. Try it on 1 host and if it works there you can do it on your other hosts too. Then you can use the <fetch_minimal_work>1</fetch_minimal_work> option in cc_config.xml which will restrict you to receiving only 1 task per core. I'll help you upgrade to 6.12.34 if you run into any trouble.

If you installed BOINC from Ubuntu repositories then you can still upgrade BOINC to 6.12.34 by downloading the Berkeley installer, installing into a temporary directory and copying ~/temp/boinc to /usr/bin/boinc_client. First rename your current /usr/bin/boinc_client to boinc_client_6.10.58 in case you want to switch back. You may have to install a few shared libs but it works. You can leave BOINC manager at 6.10.58 and it will work fine with a 6.12.34 client. I know because that's what I do on my Ubuntu machine. Directions for using the Berkeley installer are [http://boinc.berkeley.edu/wiki/Installing_BOINC#The_Berkeley_Installer]here[/url].

Also, you're asking for trouble running a project that has 50 hour tasks that don't checkpoint. I refuse to run such projects . They can bloody well make their app checkpoint if they're going to have tasks run that long. However if you really want to run their tasks then go into your BOINC preferences and set your task switch time to 50 hours or however long those tasks require. Then BOINC should run them start to finish with no interruption. If you don't want to do that then set your preferences to leave apps in memory when suspended. That way they restart where they leave off even if they don't checkpoint.

I wouldn't hold my breath waiting for this project to add the option to download however many tasks you want. I am confident you can cope with your problems using settings already available to you.

Don't be afraid to ask questions, we're here to help.

---

BOINC FAQ Service
Official BOINC wiki
Installing BOINC on Linux

Thanks Dagorath!

You're welcome, Eric. BTW, BOINC 6.12.34 is now the stable recommended version for Linux and Windows, 6.12.35 for Mac.

And I blew the URL for the Berkeley installer in my last post. Try The Berkeley Installer.

---

BOINC FAQ Service
Official BOINC wiki
Installing BOINC on Linux