I increased the WU limit from 8 to 12. This should probably make a few people happy :P

---

Thanks Travis :)

Thank you :-)

Thank you very much, Travis.

---

I am the Kittyman.

Please visit and give a Click for Seti City.

I noticed -- thanks -- simplifies things a bit for me.

---

Does this also change the daily WU limit or daily credit limit? Or just the number of WUs that a host can cache at a given time?

---

I am the Kittyman.

Please visit and give a Click for Seti City.

Cheers mate!!

---

Thanks Travis

Came back from North Wales late last night and crashed out.

Just noticed the longer caches in the boxes I still have running, and that are not currently dead for various reasons still to be identified.

This explained it all for the caches.

Does this also change the daily WU limit or daily credit limit? Or just the number of WUs that a host can cache at a given time?

It's just the size of you cache at any given time.
Makes 96 for your i7 - won't last very long I guess. :D

---

mic.

Does this also change the daily WU limit or daily credit limit? Or just the number of WUs that a host can cache at a given time?

Is anyone having a problem with the daily WU limit? If so i could increase it.

---

Is anyone having a problem with the daily WU limit? If so i could increase it.

Everyone with a 45nm quad north of 3GHz is hitting the 300 WUs per core and day limit, if he is using a fast optimized application.
Edit: At least with the single stream WUs.

Is anyone having a problem with the daily WU limit? If so i could increase it.

Everyone with a 45nm quad north of 3GHz is hitting the 300 WUs per core and day limit, if he is using a fast optimized application.
Edit: At least with the single stream WUs.

Ok, I bumped it to 1k, so we should be good for awhile :)

---

Is anyone having a problem with the daily WU limit? If so i could increase it.

Everyone with a 45nm quad north of 3GHz is hitting the 300 WUs per core and day limit, if he is using a fast optimized application.
Edit: At least with the single stream WUs.

Ok, I bumped it to 1k, so we should be good for awhile :)

Until the GPU application is ready ;)

Actually, I've just received 23 wu's all supposed to be 1 min 4 sec or 1 min 30 secs duration. They usually take 1 hr 10 mins. I had this problem some months ago and had to abort most of the wu's due to them going in to 'high priority' status and stealing time from my other projects. It looks like I'll be doing the same again.

---

All man born has the right to life and no man born has the right to take that life.

Actually, I've just received 23 wu's all supposed to be 1 min 4 sec or 1 min 30 secs duration. They usually take 1 hr 10 mins. I had this problem some months ago and had to abort most of the wu's due to them going in to 'high priority' status and stealing time from my other projects. It looks like I'll be doing the same again.

Well, this is the opposite problem so I doubt they'll run in high priority.

---

Actually, I've just received 23 wu's all supposed to be 1 min 4 sec or 1 min 30 secs duration. They usually take 1 hr 10 mins. I had this problem some months ago and had to abort most of the wu's due to them going in to 'high priority' status and stealing time from my other projects. It looks like I'll be doing the same again.

Well, this is the opposite problem so I doubt they'll run in high priority.

Mw almost always runs high priority (99%), wether 10 min or 100 min, no difference here.

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

Actually, I've just received 23 wu's all supposed to be 1 min 4 sec or 1 min 30 secs duration. They usually take 1 hr 10 mins. I had this problem some months ago and had to abort most of the wu's due to them going in to 'high priority' status and stealing time from my other projects. It looks like I'll be doing the same again.

Well, this is the opposite problem so I doubt they'll run in high priority.

Mw almost always runs high priority (99%), wether 10 min or 100 min, no difference here.

I've found that BOINC versions above 5.10.x get confused easily with MW due to the x number of WUs at a time limit, especially if you're running multiple projects at the same time.

---

Calm Chaos Forum...Join Calm Chaos Now

Does this also change the daily WU limit or daily credit limit? Or just the number of WUs that a host can cache at a given time?

Is anyone having a problem with the daily WU limit? If so i could increase it.

I have dedicated MW crunchers, and I have not seen a limit problem that I am aware of.....

But - a little increase to 400 per core might be appropriate.

Question,

Why do you have a max WU limit per day anyway? You have a limit on the cache -

---

.

No problems running in high priority.

I have never seen my quads, when they are not dead, running high priority, even when running more than 1 project (usually 2).

My only rig that occasionally goes high priotity is my 6 year old dual Xeon beast.

Actually, I've just received 23 wu's all supposed to be 1 min 4 sec or 1 min 30 secs duration. They usually take 1 hr 10 mins. I had this problem some months ago and had to abort most of the wu's due to them going in to 'high priority' status and stealing time from my other projects. It looks like I'll be doing the same again.

Well, this is the opposite problem so I doubt they'll run in high priority.

Mw almost always runs high priority (99%), wether 10 min or 100 min, no difference here.

What have you set your connect preference and additonal work buffer preference too?

Since MW has short deadlines (3 days) you can't set these so that you have more than about 1.25 days of work cached, otherwise BOINC will crunch the short deadline wu's in high priority. This is a similar situation for MalariaControl as well.