I noticed that, prior to the outages, I was crunching short running WU's only...

I only have a view on the half hour prior to the outage of 3h40 and at that time I was in bed, so no live view...

And no, I don't have a script deleting longer, normal WU's.

I noticed that all the work was short WU's, and that put a load on the server that would have been like a denial of service attack.

If we were allowed to download more work, say 24 WU's per core and then denied any more work for the next 5 minutes instead of 1 minute, the servers would be spared all the fast machines asking for work every minute. I would guess that the servers can give out 5 WU's per request almost as easily as 1.

That should take a great load off the servers. I have my cache set to 0.02 days so I don't ask for work when there is no completed work.

The trouble then is that the CPU's can be run out of work on other projects.

---

...

If we were allowed to download more work, say 24 WU's per core and then denied any more work for the next 5 minutes instead of 1 minute, the servers would be spared all the fast machines asking for work every minute. I would guess that the servers can give out 5 WU's per request almost as easily as 1.

That should take a great load off the servers. I have my cache set to 0.02 days so I don't ask for work when there is no completed work.

The trouble then is that the CPU's can be run out of work on other projects.

From a users perspective it sounds like a good idea, but the project admins have previously told us that if there are too many wu's in the DB it slows down the accessing of the DB leading to crashes which causes us all problems. So until the server gets a boost (if ever) we are stuck with what we have.

Looks like it's down again, for at least the last 5 hours.

---

I thought it was just me getting that.....

---

I am too...

---

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

This loss of work has been going on for many hours now, and [b]the server status makes it look like it will continue.[b]

It is time for sleep so I will run Collatz until I am awake and can revert, assuming the servers are back

---

Go away, I was asleep

Damn! And just when my RAC had hit record levels!

I wonder if Collatz will fall over with the influx of users.....

Damn! And just when my RAC had hit record levels!

Ohh, you poor fella! ;p

---

This time I was closing in on 100,000 RAC.

New video cards tend to do that.

---

Database has been in down for maintenance for a few hours???

I'm trying to figure out what exactly happened. Hopefully I'll have more info available later when I hear from labstaff.

Exiled to the mines of Cosmo.

---

me@rescam.org

Here we go again with an outage of indefinite length with an information outage as well. And the load shift over to Collatz has the same effect...

---

Nothing from Travis and the prosjekt is still down.

Getting on for 24 hours now

---

Go away, I was asleep

Here we go again with an outage of indefinite length with an information outage as well. And the load shift over to Collatz has the same effect...

Collatz seems slow but finished work is getting Uploaded and new work Downloaded on my Box's, very slowly though ...

---

STE\/E

Here we go again with an outage of indefinite length with an information outage as well. And the load shift over to Collatz has the same effect...

Collatz seems slow but finished work is getting Uploaded and new work Downloaded on my Box's, very slowly though ...

Yes, Collatz hp is down nearly, but you get work and can send work. So the important thinks work ;) I have 20 WU´s like allways.

But i also think, that there should be a news with updates on the mainpage!

90% off my GPU time should be used for MW, so i often just stop Collatz to fetch new work (YES i know not the best way ;) ). So i waste yesterday about 2 hours of GPUtime. Idle sucks :/

EDIT: Ok Collatz is down atm ;( no report or new work ;(

Lol, maybe today wasn't the best launch date for my new cruncher. Collatz seems down too, stuck at uploading/downloading

---

"Government big enough to supply everything you need is big enough to take everything you have."
-Thomas Jefferson
American Thinker

This seems quite predictable. MW goes offline, unannounced, unexplained and with no news updates as to what is going on or when (if) it will be resolved. That then spurs a flock of 90/10 MW/Collatz folks to go 100% Collatz.

Collatz, inundated by the tsunami of temporary MW refugees, gets swamped and encounters surge load problems that it as a one person unfunded shop can't readily handle.

The interesting thing is that typically not only does Collatz seem to recover from the surge before MW is back on line, Collatz provides an explanation as to what happened for them long before we get blessed with an explanation over here.

Personally, MW became my number 2 project some time ago, thanks to Collatz support for single precision GPU AND the proactive communication available over there.

I get the impression that if MW loaned Collatz some of its resources that would project planning/operation and communications training that would have value for them here in MW land.

---

"90% off my GPU time should be used for MW, so i often just stop Collatz to fetch new work (YES i know not the best way ;) ). So i waste yesterday about 2 hours of GPUtime. Idle sucks :/"

skysnake, please excuse the out of place post: maybe I misunderstand, but how are you setting 90% gpu for mw having collatz as another share? I have had no success running collatz with mw in that collatz takes over no matter how I set the sharing. I read that it might be a boinc problem, but whatever it is collatz dictates on my machine if running. that is not happening to you?


thanks.

"90% off my GPU time should be used for MW, so i often just stop Collatz to fetch new work (YES i know not the best way ;) ). So i waste yesterday about 2 hours of GPUtime. Idle sucks :/"

skysnake, please excuse the out of place post: maybe I misunderstand, but how are you setting 90% gpu for mw having collatz as another share? I have had no success running collatz with mw in that collatz takes over no matter how I set the sharing. I read that it might be a boinc problem, but whatever it is collatz dictates on my machine if running. that is not happening to you?


thanks.

NP ;)

The problem is very simpel. A MW WU takes about 1:40 and a Collatz WU about 5:40
MW allows 12 WU´s max. Collatz about 20 or more. So i spend allways more time for collatz, because if a WU is uploaded, a new WU is downloaded. Perhaps just chance the preferences should help, but i haven´t try it yet.