Did either of you two read Matt's explanation?

Perhaps one of you could design a better feeder?

FWIW, every machine of mine that has needed more work today has received plenty - just maybe not at the first attempt.

Richard, my point was that I was getting a "wrong" message, since the indicators showed that 1) RTS was nominal and 2) I was getting "no work" messages.

Of course, right after I wrote that note, I got the fill that my quad was asking for for the previous 8 hours. (==> There is no predictive ability from the system indicators.)

OK, so the problem (in devising a suitable message) is:

Sometimes there is work on the shelf ready for collection, and more work in the stockroom. That's the ideal.
Sometimes there is no work anywhere. That's what the current message effectively conveys.
And finally, there is the situation Matt describes: there is work in the stockroom, but the errand-boy (feeder) hasn't had time to fill the shelves since the last customer left.

I can see why you might want a different message for case (3), but what would be the best wording for the casual (non-technical) user?

We don't need better wording, but that might be nice. We need a more predictive set of statistics (better term would be monitors) so that we can better infer the status of the project and our own clients.

We don't need better wording, but that might be nice. We need a more predictive set of statistics (better term would be monitors) so that we can better infer the status of the project and our own clients.

I would prefer that SETI's limited server power is dedicated to shifting the work as needed, rather than maintaining a second-by-second (instead of the current hour-by-hour) status page.

We don't need better wording, but that might be nice. We need a more predictive set of statistics (better term would be monitors) so that we can better infer the status of the project and our own clients.

I would prefer that SETI's limited server power is dedicated to shifting the work as needed, rather than maintaining a second-by-second (instead of the current hour-by-hour) status page.

In my (likely unpopular) opinion, this is a case where we need less information.

A work request that isn't filled is not a failure, and if it did not show up in the logs we would not have so many threads about not getting work.

It isn't an error condition. It's a missed opportunity to "top off" the queue.

It only becomes a problem when you drop below one work unit per core.

I don't know how often per second the feeder loads up the scheduler, but I'm thinking that a second-by-second status might not be enough to do what PhonAcq wants -- and we'd need to know about the feeder queue too.

---

Completely out of WUs. Let's rest :)

I just thought of something...

With AP being basically offline like it is, isn't this what Matt wanted to do to avoid the 4.36>5.00 changeover fiasco? Stop the splitters, let the work run dry (for AP only), and then start everyone fresh on 5.00.

He shut the AP splitters off and then someone turned them back on the next day.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

We don't need better wording, but that might be nice. We need a more predictive set of statistics (better term would be monitors) so that we can better infer the status of the project and our own clients.

I would prefer that SETI's limited server power is dedicated to shifting the work as needed, rather than maintaining a second-by-second (instead of the current hour-by-hour) status page.

Again, not my point. If the monitors we keep are not useful, lets replace them. At times I think they are just eye candy. When I try to understand what they are saying, they tend to be saying very little. Usually because some events going on are corrupting them, as for example what happens when seti runs out of usable storage.

I haven't run Seti in a while but I came back to it as part of our Project of the Month. The way I see things now according to the server status page:
No WU's available.
None being created.
Half the splitters turned off.
Tomorrow is a down for Maintenance day which means everything will be even more screwed up.
And forgert the crap about the storeroom and the shelves. If there is nothing in the storeroom you can NOT put it on the shelves.

Bottom line, my 8 GTX260 GPU's are going back on GPUGrid Thursday. I will let my CPU's continue to crunch in support of my team but I will not waste my time and my GPU time trying to babysitting Seti

---

I haven't run Seti in a while but I came back to it as part of our Project of the Month. The way I see things now according to the server status page:
No WU's available.
None being created.
Half the splitters turned off.
Tomorrow is a down for Maintenance day which means everything will be even more screwed up.
And forgert the crap about the storeroom and the shelves. If there is nothing in the storeroom you can NOT put it on the shelves.

Bottom line, my 8 GTX260 GPU's are going back on GPUGrid Thursday. I will let my CPU's continue to crunch in support of my team but I will not waste my time and my GPU time trying to babysitting Seti

Bitter much?

---

You will be assimilated...bunghole!

Fair enough - your choice. Nobody's forcing you to volunteer here.

That'll relieve the pressures on the server a bit.

I haven't run Seti in a while but I came back to it as part of our Project of the Month. The way I see things now according to the server status page:
No WU's available.
None being created.
Half the splitters turned off.
Tomorrow is a down for Maintenance day which means everything will be even more screwed up.
And forgert the crap about the storeroom and the shelves. If there is nothing in the storeroom you can NOT put it on the shelves.

Bottom line, my 8 GTX260 GPU's are going back on GPUGrid Thursday. I will let my CPU's continue to crunch in support of my team but I will not waste my time and my GPU time trying to babysitting Seti

Don’t take it personally. I know from experience that these guys’ barks are far worse than their bites (bytes?)

Seti has (had, always will have) server/bandwidth issues. One of the biggest projects, running on a shoe-string budget after all.

Perhaps, for the month, set your preference for Seti to a large number and GPUGrid to a much lower number. That way, if SETI is available, it will crunch for the good of your team, if not then your machines will still be busy with GPUGrid.

Peace.

---

Pure mathematics is, in its way, the poetry of logical ideas.

Albert Einstein

I'll endorse KenzieB's idea.

And being philosophical in nature, I've concluded that if seti's system worked 'perfectly', then none of us would be scanning these boards for a diversion. So a constant series of system hiccups might be good for all us, like chicken soup!

I'll endorse KenzieB's idea.

And being philosophical in nature, I've concluded that if seti's system worked 'perfectly', then none of us would be scanning these boards for a diversion. So a constant series of system hiccups might be good for all us, like chicken soup!

Yes, I'll go with that!

From the message board tech page the servers are overloading bandwidth from the 1000 wu oversend from 1? week ago. He is saying that they are getting page faults from to many work units being returned. link http://setiathome.berkeley.edu/forum_thread.php?id=51799 Relax a little and breath some. They have had a problem also with the HDs coming from Arcibo this weekend. Some one came in and got files from the offsite backup archive. The archive had been offline for upgrades/repairs see this link http://setiathome.berkeley.edu/forum_thread.php?id=51714 Yeah it will be a little bumpy for the next few day bet it will be settled by wed or thursday

---

I'll endorse KenzieB's idea.

And being philosophical in nature, I've concluded that if seti's system worked 'perfectly', then none of us would be scanning these boards for a diversion. So a constant series of system hiccups might be good for all us, like chicken soup!

Well it does keep us from running in the streets in packs late at night, terrifying the local citizenry.

A little off-topic but, who remembers the great Thumper death of a couple years ago. (May ‘07, I think.) Over a week with no work at all!!! We all survived. (I only remember because I was new, and naive in the ways of all things BOINC.)

Like B-Man says: Relax and Breathe.

Also, Linking your link to Matt L’s Tech Thread post. :o)

---

Pure mathematics is, in its way, the poetry of logical ideas.

Albert Einstein

Well it does keep us from running in the streets in packs late at night, terrifying the local citizenry.

Speak for yourself!

A little off-topic but, who remembers the great Thumper death of a couple years ago. (May ‘07, I think.) Over a week with no work at all!!! We all survived. (I only remember because I was new, and naive in the ways of all things BOINC.)

Yep. I was there.

A little off-topic but, who remembers the great Thumper death of a couple years ago. (May ‘07, I think.) Over a week with no work at all!!! We all survived. (I only remember because I was new, and naive in the ways of all things BOINC.)

Yep. I was there.

As was I, but if I remember correctly... I was using a 5-day cache and got very close to running out of work in the cache, but the WUs started flowing again when I only had one more in reserve. I came close to running out, but kept my two rigs running (Athlon 1100 and Athlon XP 2400+ at the time).

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

A little off-topic but, who remembers the great Thumper death of a couple years ago. (May ‘07, I think.) Over a week with no work at all!!! We all survived. (I only remember because I was new, and naive in the ways of all things BOINC.)

Yep. I was there.

As was I, but if I remember correctly... I was using a 5-day cache and got very close to running out of work in the cache, but the WUs started flowing again when I only had one more in reserve. I came close to running out, but kept my two rigs running (Athlon 1100 and Athlon XP 2400+ at the time).

Well, I was new at the time and still hadn't figured out how to increase my cache and was running with whatever came as standard.

After my cache ran dry I did, however, discover BOINC's main pupose: Have multiple projects. LOL.

---

Pure mathematics is, in its way, the poetry of logical ideas.

Albert Einstein

I'll endorse KenzieB's idea.

And being philosophical in nature, I've concluded that if seti's system worked 'perfectly', then none of us would be scanning these boards for a diversion. So a constant series of system hiccups might be good for all us, like chicken soup!

Well it does keep us from running in the streets in packs late at night, terrifying the local citizenry.

A little off-topic but, who remembers the great Thumper death of a couple years ago. (May ‘07, I think.) Over a week with no work at all!!! We all survived. (I only remember because I was new, and naive in the ways of all things BOINC.)

Like B-Man says: Relax and Breathe.

Also, Linking your link to Matt L’s Tech Thread post. :o)

I remember hearing about it, but I also remember not caring that much as I have enough projects attached to ride out almost any conceivable outage.

---

BOINC WIKI

The point everyone seems to miss in distributed computing iu you donating your spare CPU cycles for scientists to use as they need to analize data. This is not an on line game where the "company" provides servers for you to rack up points and win. It's become that, but it shouldn't be. Maybe the so;ution is like the online game community for those that demand units available and 24/7 support that they make a "pay to play" server so you all can play the game.

We're helping them folks, they aint a help desk for us....

---