That was the case when Classic started but at the time the Boinc Seti started, the dialups were long gone.

Broadband here has only really taken off in the last 15 years or so.

Classic also ended about 15 years ago.

Around midnight UTC the assimilators started assimilating again. Now the assimilation queue is finally shrinking! And pretty fast too.

That was the case when Classic started but at the time the Boinc Seti started, the dialups were long gone.

Broadband here has only really taken off in the last 15 years or so.

Classic also ended about 15 years ago.

I notice you left this bit off of the quote "Almost 50% of internet users were still on dial up in 2006." And there were many other countries around the world that lagged well behind us.
But i guess they don't count.

---

Grant
Darwin NT

Around midnight UTC the assimilators started assimilating again. Now the assimilation queue is finally shrinking! And pretty fast too.

Some are being disposed of, certainly, but it's still hit and miss. I've seen some resends go through this morning, and they've already been purged from the visible database. But WUs like 3953335831 went through 2½ days ago, and are still showing.

We'll still need a big spring-clean when the last WU validates - and I'm not saying which Spring.

Around midnight UTC the assimilators started assimilating again. Now the assimilation queue is finally shrinking! And pretty fast too.

Some are being disposed of, certainly, but it's still hit and miss. I've seen some resends go through this morning, and they've already been purged from the visible database. But WUs like 3953335831 went through 2½ days ago, and are still showing.

Assimilators work in workunit creation date order (database id order). So they process newest work last. Resent tasks have generally very old workunits because they have already timed out at least once, so they jump the queue and get assimilated fast.

Now the database size has dropped below the old standard 20 million result limit, so any further server issues can't be explained by database bloat.

My oldest valid task awaiting assimilation is over 16 days since both results were returned :
https://setiathome.berkeley.edu/workunit.php?wuid=3944544179

I'm fairly sure that someone can beat that !

Around midnight UTC the assimilators started assimilating again. Now the assimilation queue is finally shrinking! And pretty fast too.

and the ratio at which the results validation queue and the workunits assimilation queue have reduced is about 2.3:1

非常有意思

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

one oldest from the 25th of March , and oldest waiting wingman from the 1st of January

---

My oldest from 7 December and awaiting a wingman till the middle of May.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

My oldest valid task awaiting assimilation is over 16 days since both results were returned :
https://setiathome.berkeley.edu/workunit.php?wuid=3944544179

I'm fairly sure that someone can beat that !

That one has gone now, https://setiathome.berkeley.edu/workunit.php?wuid=3944893567 should go in the next 6-12 hours or less

Seems like 16 days is the average assimilation delay on recent tasks at the moment.

I'll never make any sense of of some of these showing up. Just glad this one expires tomorrow.
https://setiathome.berkeley.edu/workunit.php?wuid=3934853925

Now things should improve quickly, once the purgers catch up with the load that will be heading their way.

Results out in the field                  2,451,796
Results returned and awaiting validation 13,797,784
Workunits waiting for assimilation        5,070,591

But we'll still be waiting months for all those resends to clear the "Results out in the field" numbers.

---

Grant
Darwin NT

Now things should improve quickly, once the purgers catch up with the load that will be heading their way.

Results out in the field                  2,451,796
Results returned and awaiting validation 13,797,784
Workunits waiting for assimilation        5,070,591

But we'll still be waiting months for all those resends to clear the "Results out in the field" numbers.

. . Not if they chop the deadlines

Stephen

. .

I would be surprised if they chop deadlines simply because it would involve work. I am sure they have other more important things to do, however I could be wrong

---

But we'll still be waiting months for all those resends to clear the "Results out in the field" numbers.

. . Not if they chop the deadlines

I figure it would take a lot more effort than making use of the existing function to reduce the deadline on resends, and that hasn't happened so i'd be surprised if they have another go at getting existing work to timeout early.

---

Grant
Darwin NT

I would be surprised if they chop deadlines simply because it would involve work. I am sure they have other more important things to do, however I could be wrong

. . As on Mythbusters, failure is always an option ... :)

Stephen

:)

But we'll still be waiting months for all those resends to clear the "Results out in the field" numbers.

. . Not if they chop the deadlines

I figure it would take a lot more effort than making use of the existing function to reduce the deadline on resends, and that hasn't happened so i'd be surprised if they have another go at getting existing work to timeout early.[/quote]

. . Sadly it is looking that way :)

Stephen

:(

I'll never make any sense of of some of these showing up. Just glad this one expires tomorrow.
https://setiathome.berkeley.edu/workunit.php?wuid=3934853925

Less than two hours left on this one. I'm wondering if it will be redistributed or just time out gracefully.

Haven't gotten anything in about 16 hours. My slow machine still has about 30 hours of CPU work, and roughly 91 hours of intel_gpu work when that is done, and I'm out.

Forums slowed to a crawl & then the website went MIA. Was it a glitch or are we about to crash & burn again?

---

Grant
Darwin NT