I have a question:

People ARE uploading, right? Or is nobody able to upload because of all of the request packets?

I should at least hope that SOME people are uploading.

I've had uploads go through after a few automatic retries.

---

I've throttled my uploads on most of my hosts to a few hours a day, and run a larger cache to span the frequent days of berkeley blues. Things more or less work ok, albeit lots of no-connects and no-work messages occur during those hours. Doing so, I'm trying to be part of the solution and not part of the problem, I guess.

I have a question:

People ARE uploading, right? Or is nobody able to upload because of all of the request packets?

I should at least hope that SOME people are uploading.

Admittedly, I don't crank through work like most on here, but I've had all of my pending uploads complete today.

---

I have a question:

People ARE uploading, right? Or is nobody able to upload because of all of the request packets?

I should at least hope that SOME people are uploading.

Yes. Automatically. And well before the deadlines. That is all that really matters anyway.

---

You guys can have my bandwidth. I supended seti. I'll detach soon so the wu's get resent.

OK -- excellent -- I can understand the interest in Biological sciences -- as I noted before, I'm a cancer survivor (4 years now since surgery), and in addition, my wife is a psychiatrist in private practice. She also teaches in the Religious Studies department at the University here, but I've not found any projects seeking to respond to religious issues <smile>.

I can answer that very honestly for you: not at all. I'm not the type of person that likes to create "cliques" and then attack those whom are not part of it. I fully support everyone's right to do as they wish, including not making SETI their primary project. In fact, my gf has insisted she has wanted to make other projects our primary, but not because of server problems, rather because of her interest in other sciences - namely biological sciences finding cures to diseases. She has a vested interest in this subject because her family owns the Intermediate Health Care facility for the Mentally Ill that I work at.

---

Wow I am disappointed...

All the Doom and Gloom Sayers have not had issues/said anything for a while.

I do not know what to report as Curent Issues.

Regards

---

Please consider a Donation to the Seti Project.

Wow I am disappointed...

All the Doom and Gloom Sayers have not had issues/said anything for a while.

I do not know what to report as Curent Issues.

Regards

I honestly don't know what to say......

My main cruncher has been running better than ever since the holiday weekend.

All my uploads go through, my cache is full......and she keeps crunching away.

The only problem I have is that I have had to SUSPEND alot of tasks manually in an attempt to force BOINC to crunch tasks that are coming closer to their report deadlines.

For instance, I have a bunch of 'July 12' due work and for some reason, without my intervention and suspension of tasks.....BOINC would rather work on 'July 30' deadline tasks.

I have also made good use of ReSchedule 1.7 and have not Vlar Killed a single WU......I have saved and ReScheduled 100% of them that downloaded to my rig.

Anyways, that is all.
Allan

---

I am TCP JESUS...The Carpenter Phenom Jesus....and HAMMERING is what I do best!
formerly known as...MC Hammer.

The only problem I have is that I have had to SUSPEND alot of tasks manually in an attempt to force BOINC to crunch tasks that are coming closer to their report deadlines.

BOINC runs a simulation based on the projected time left to crunch. It looks at the projected run-times, stacks 'em up, and compares the projected completion against the due dates.

If the simulation shows that some work will be finished near the deadline, or that deadlines will be missed, it shifts from doing work in FIFO order to doing work in deadline order.

BOINC doesn't always work in deadline order because devoting too much time on short-deadline tasks runs the risk of running out of time for the long-deadline tasks.

I know, it's hard to sit back and watch when it seems like BOINC is doing work in the wrong order, but if you do let it go, let it do the work in the order it wants, you might be pleasantly surprised.

---

Wow I am disappointed...

All the Doom and Gloom Sayers have not had issues/said anything for a while.

I do not know what to report as Curent Issues.

Regards

Perhaps they RTFM'd?

---

The only problem I have is that I have had to SUSPEND alot of tasks manually in an attempt to force BOINC to crunch tasks that are coming closer to their report deadlines.

BOINC runs a simulation based on the projected time left to crunch. It looks at the projected run-times, stacks 'em up, and compares the projected completion against the due dates.

If the simulation shows that some work will be finished near the deadline, or that deadlines will be missed, it shifts from doing work in FIFO order to doing work in deadline order.

BOINC doesn't always work in deadline order because devoting too much time on short-deadline tasks runs the risk of running out of time for the long-deadline tasks.

I know, it's hard to sit back and watch when it seems like BOINC is doing work in the wrong order, but if you do let it go, let it do the work in the order it wants, you might be pleasantly surprised.

So it's better to just leave it run without intervention then ?

I thought that because I use ReSchedule, THAT might be the cause of some small issues, such as the working order I am experiencing....

I have noticed quite a few WAITING TO RUN (started) WU's left behind....more than usuall. Is this a side effect of using ReSchedule ?

Allan

---

I am TCP JESUS...The Carpenter Phenom Jesus....and HAMMERING is what I do best!
formerly known as...MC Hammer.

I know, it's hard to sit back and watch when it seems like BOINC is doing work in the wrong order, but if you do let it go, let it do the work in the order it wants, you might be pleasantly surprised.

So it's better to just leave it run without intervention then ?

I think so.

There is a fairly healthy "safety margin" in the calculations. I've tried very hard to fool BOINC into over-requesting work, and even cheating (tweaking the Duration Correction Factor by a couple of orders of magnitude) it's pretty hard to get the scheduler into a corner it can't 'crunch' out of.

---

This is tough. I see links to the Cricket Graphs in a LIVE Format. Seti does not own or maintain those servers, if a User wants to look that is one thing. Embedding them in this Forum or any other is NOT.

At this point I am going to hide all posts that contain the embedded live links. In the future if I see them again, I am going to recommed to my fellow Moderators that a Ban Vote be Started. People were warned before. Strike 2

If you want the Url to go look on a personal basis that is fine. Here is the URL
http://fragment1.berkeley.edu/newcricket/grapher.cgi?target=/router-interfaces/inr-250/gigabitethernet2_3&view=Octets Please Bookmark/Favorites it. You can sapture a grphics and then repost it, that is fine.

Regards

Now I have to go hide messages as it creates network traffic that is not aceptable.

---

Please consider a Donation to the Seti Project.

Sorry I don't think I saw the original post You were talking about as I wasn't around a lot not too long ago(nor do I need to now), But in any case If I post a graph It won't be live, It'll be quite dead. :D

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

I see it is the weekend again back to connect failures again, so just sit and hope they will go up.

---

There are cases where the manual retry is necessary

Then perhaps after the server has failed to respond, the retry button for that project should be disabled for as long as the automatic backoff is enacted.

Oh God, no. I have enough projects that are on the 24 hour back-off already. After the 24 hour back-off, BOINC tries once to contact the project and goes off into another 24 hour back-off.

When at any other time there is work, but not at the time my 24 hour back-off finishes, I wouldn't be able to break that loop ever again. I'd have to detach and reattach, as not even a project reset will reset the 24 hour back-off. It'll silently continue to count down under the properties of the project.

---

Something broken?
Network traffic has dropped off. Just gone through the 24:00hr point with hardly a blip in traffic (even when things are quiet it usually takes it to the limit for a while).
Server status page shows several AP splitters not running.

---

Grant
Darwin NT

They don't run when there's no more AP files to split on disk.

I'm guessing a channel can only be done by one splitter then- 1 channel still in progress. All others done, no new ones left to process.

The Server status page hasn't updated for almost 2 hours either.

Just noticed that.

---

Grant
Darwin NT

Couldn't find a thread about "no panic", so I'm posting here.

As of midnight Friday UTC the Cricket graphs have smoothed right out below max, and all my uploads are going through on the first try. Not getting any downloads, probably because I have a few dozen shorty MB WUs running in high priority mode.

So, what did the Boys in Berkley do to bring about this sudden calmness?

---