I am just curious to know why we need the work units purged results to clear? These will probably take 24 hours. Apart from people having lots of results in their accounts I cannot see any other major issue, unless we run out of disk space.

It's more that records in the database tables need to clear - and in particular, the indexes to the records need to be shrunk until they fit in RAM (not on disk). Otherwise, they will be unutterably slow.

If it can't fit into RAM where does it go?

---

LOL. You only have 16 tasks outstanding in the database. I have 55,000 outstanding in the database.

---

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

A proud member of the OFA (Old Farts Association)

I am just curious to know why we need the work units purged results to clear? These will probably take 24 hours. Apart from people having lots of results in their accounts I cannot see any other major issue, unless we run out of disk space.

It's more that records in the database tables need to clear - and in particular, the indexes to the records need to be shrunk until they fit in RAM (not on disk). Otherwise, they will be unutterably slow.

If it can't fit into RAM where does it go?

If the indexes can't fit into RAM, they have to be read off slow drive storage. Thus unutterably slow as Richard described.

---

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

A proud member of the OFA (Old Farts Association)

I am just curious to know why we need the work units purged results to clear? These will probably take 24 hours. Apart from people having lots of results in their accounts I cannot see any other major issue, unless we run out of disk space.

It's more that records in the database tables need to clear - and in particular, the indexes to the records need to be shrunk until they fit in RAM (not on disk). Otherwise, they will be unutterably slow.

If it can't fit into RAM where does it go?

If the indexes can't fit into RAM, they have to be read off slow drive storage. Thus unutterably slow as Richard described.

Thanks Keith. I guess if people want it they could start a fundraiser

---

LOL. You only have 16 tasks outstanding in the database. I have 55,000 outstanding in the database.

Hey... be nice... my mac mini is proud of every one of the tasks it does. It may be old and slow but it has done a bunch of WUs over many years.

But I'm still not sure why you see more than 24 hours of valids? Maybe your machine spits them out so fast that you have a long list of pending... just wanting around on the partner machine (probably something slow like mine).

It wouldn't cost the db much to show me more than 24 hours of history.

edit : ah my misunderstanding. thought you guys were talking about valids, not pendings

Thanks Keith. I guess if people want it they could start a fundraiser

Many of us would respond if we only knew it would improve things.
I, for example, have donated towards specific ends.
I await further introductions towards a new improvement.

---

"Time is simply the mechanism that keeps everything from happening all at once."

Purging is the tasks list we get to see after they have been validated assimilated and files removed.
I believe it is set to 7 days for MB and 2 days for AP.

It would be nice if the limit was 6 days, so that the big surge of tasks after maintenance is removed before the next round comes in.

How weird. my task list for validated tasks is only 24 hours long... MB or AP

. . Pretty much what I am seeing too.

Stephen

.

I am just curious to know why we need the work units purged results to clear? These will probably take 24 hours. Apart from people having lots of results in their accounts I cannot see any other major issue, unless we run out of disk space.

It's more that records in the database tables need to clear - and in particular, the indexes to the records need to be shrunk until they fit in RAM (not on disk). Otherwise, they will be unutterably slow.

If it can't fit into RAM where does it go?

. . Umm, it is on disk. That is what makes access to it slow ...

Stephen

. .

LOL. You only have 16 tasks outstanding in the database. I have 55,000 outstanding in the database.

. . Now I am LOL, that is the output of a small country ... :)

Stephen

:)

LOL. You only have 16 tasks outstanding in the database. I have 55,000 outstanding in the database.

Hey... be nice... my mac mini is proud of every one of the tasks it does. It may be old and slow but it has done a bunch of WUs over many years.

But I'm still not sure why you see more than 24 hours of valids? Maybe your machine spits them out so fast that you have a long list of pending... just wanting around on the partner machine (probably something slow like mine).

It wouldn't cost the db much to show me more than 24 hours of history.

edit : ah my misunderstanding. thought you guys were talking about valids, not pendings

My oldest pending was returned 19 July. WU 3058299862

My oldest valid is from 18 July WU 3056429782

---

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

A proud member of the OFA (Old Farts Association)

LOL. You only have 16 tasks outstanding in the database. I have 55,000 outstanding in the database.

. . Now I am LOL, that is the output of a small country ... :)

Stephen

:)

The effect of 16 gpus running the Linux special app.

---

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

A proud member of the OFA (Old Farts Association)

No, every machine, however minimal, crunches toward the goal. I have 2 Android tablets and a Android phone crunching too. Their output is not even a rounding error compared to the PC's but even they add to my account total.

edit : ah my misunderstanding. thought you guys were talking about valids, not pendings

Every task assigned to your account, In Progress, Pending, Inconclusive, Invalid and Errors have to be held in the database indices. So the larger the quantity of records that have to be pulled the slower the retrieval. If the Results and WU would be purged faster, the smaller the retrieval transaction and my web pages might actually appear when I click on them. I can only wish.

---

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

A proud member of the OFA (Old Farts Association)

The servers started making progress on the Results awaiting purging around Zulu 3 November today from the Haveland graphs. I could actually pull up my oldest tasks, though it took a minute or so for the web page to appear.

---

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

A proud member of the OFA (Old Farts Association)

I am just curious to know why we need the work units purged results to clear? These will probably take 24 hours. Apart from people having lots of results in their accounts I cannot see any other major issue, unless we run out of disk space.

It's more that records in the database tables need to clear - and in particular, the indexes to the records need to be shrunk until they fit in RAM (not on disk). Otherwise, they will be unutterably slow.

If it can't fit into RAM where does it go?

. . Umm, it is on disk. That is what makes access to it slow ...

Stephen

. .

I thought it was on disk as well

---

LOL. You only have 16 tasks outstanding in the database. I have 55,000 outstanding in the database.

Hey... be nice... my mac mini is proud of every one of the tasks it does. It may be old and slow but it has done a bunch of WUs over many years.

But I'm still not sure why you see more than 24 hours of valids? Maybe your machine spits them out so fast that you have a long list of pending... just wanting around on the partner machine (probably something slow like mine).

It wouldn't cost the db much to show me more than 24 hours of history.

edit : ah my misunderstanding. thought you guys were talking about valids, not pendings

My oldest pending was returned 19 July. WU 3058299862

My oldest valid is from 18 July WU 3056429782

Apples and Oranges, I think...
Your oldest pending has only been pending (inconclusive) for 2 hours, as that's when the wingman reported, creating something to be pending rather than in process.
Likewise, your oldest valid has only been valid for 6 hours, as that's when the wingman reported that would compare against two previous results to resolve an inconclusive.
It's the most recent activity that counts, not just yours.
Or did I misunderstand your point?

---

I thought it was on disk as well

It is, and that's the problem. Until it is read in to memory then any access is extremely slow. If it doesn't all fit in to memory, then it has to be read from (and written to) disk instead- which is orders of magnitude slower than memory, particularly for random reads & write.

---

Grant
Darwin NT

My oldest valid is from 18 July WU 3056429782

Apples and Oranges, I think...
Likewise, your oldest valid has only been valid for 6 hours, as that's when the wingman reported that would compare against two previous results to resolve an inconclusive.

Agreed. That one should be purged at 4 Nov 2018, 01:32 UTC - 24 hours after it was validated. I'll be asleep in bed, but if anyone wants to check, they can work out how long the backlog is at that time.

edit : ah my misunderstanding. thought you guys were talking about valids, not pendings

My oldest pending was returned 19 July. WU 3058299862

My oldest valid is from 18 July WU 3056429782

. . Sorry Keith but that valid is from the 3rd November 2018. Prior to that it was an inconclusive. Before that it was a pending because you had two dud wingmen that timed out. And back to my pet gripe .... funny how it keeps turning up.

Stephen

:(

If it can't fit into RAM where does it go?

. . Umm, it is on disk. That is what makes access to it slow ...
Stephen

I thought it was on disk as well

. . If it cannot fit into RAM it is ONLY on disk, ... hence slow ...

Stephen

. .

LOL. You only have 16 tasks outstanding in the database. I have 55,000 outstanding in the database.

Hey... be nice... my mac mini is proud of every one of the tasks it does. It may be old and slow but it has done a bunch of WUs over many years.

But I'm still not sure why you see more than 24 hours of valids? Maybe your machine spits them out so fast that you have a long list of pending... just wanting around on the partner machine (probably something slow like mine).

It wouldn't cost the db much to show me more than 24 hours of history.

edit : ah my misunderstanding. thought you guys were talking about valids, not pendings

. . In that case it is not a matter of purging the database as they will remain until the last lame duck wingman completes the task or times out and someone else does. And that could be years ... :( {as in where one dud wingman times out on a task only to have it pass to another delinquent host and then another ... etc}. Which brings me back to an old bug bear of mine about deadlines ... :)

Stephen

. . Message from earlier got stuck when my PC crashed (again) due to temp problem.

:(