And we will be totally out of work in a few minutes, if no more task are added.
It'll be nighty night :-)

This one is partly to blame, adding new computers all the time (179 now, but will be more tomorrow), filling them to the brim with tasks, and never finish any tasks (a few maybe on a few of his computers)

https://setiweb.ssl.berkeley.edu/beta/hosts_user.php?sort=rpc_time&rev=0&show_all=1&userid=1445

And all the Windows machines are identical in every way, and so are the linux ones, not sure what is going on there or why. Still I suppose all the tasks will time out, eventully

---

And we will be totally out of work in a few minutes, if no more task are added.
It'll be nighty night :-)

This one is partly to blame, adding new computers all the time (179 now, but will be more tomorrow), filling them to the brim with tasks, and never finish any tasks (a few maybe on a few of his computers)

https://setiweb.ssl.berkeley.edu/beta/hosts_user.php?sort=rpc_time&rev=0&show_all=1&userid=1445

And all the Windows machines are identical in every way, and so are the linux ones, not sure what is going on there or why. Still I suppose all the tasks will time out, eventully

One thought, perhaps school computers that have the disk image replaced every day and it also replaces the BOINC directory so it is seen as new every day.

Looking at the history of his computers. This pattern has repeated every few years, set up a series of computers over a few months, then vanish from the air. Rinse, repeat.
Just now he appears to be actively abandoning tasks on at least one of the recent computers.
He does much the same on main, but over there he has had over 800 computers.
Is he a "transient visitor to an institution"???

How about a stats dump for Beta?
The last one was 02-Apr-2019 11:11 (11:10)
https://setiweb.ssl.berkeley.edu/beta/stats/

The questions are:

1. Will the database survive the night?
2. Will the database survive until the normal Tuesday outage/outrage?

More than 9-days now, since we had a stats dump for Beta.
https://setiweb.ssl.berkeley.edu/beta/stats/

Not good for those of us who follow our progress on any stats site.

More than 9-days now, since we had a stats dump for Beta.
https://setiweb.ssl.berkeley.edu/beta/stats/

More than 10-days now. :-(
Please fix the stats dumping, or I will shoo* the first ET being we find. (or his pet)

I sincerely hope the stats dump isn't fixed any time soon. Beta is for testing software on as many different platforms as possible, it is not for competitive crunching, use main for that.

I sincerely hope the stats dump isn't fixed any time soon. Beta is for testing software on as many different platforms as possible, it is not for competitive crunching, use main for that.

Agreed, Beta is for testing software — But how are we, the users, going to know if our work for Beta is productive (as in "working", and not producing bad results...) if the stats export is off? Also, the longer the stats export is off, the larger the bump when the export is eventually are but back online... This screws up your daily average on most of the stats sites!

Besides, isn't the stats dump one of the programs being tested?

---

And we will be totally out of work in a few minutes, if no more task are added.
It'll be nighty night :-)

This one is partly to blame, adding new computers all the time (179 now, but will be more tomorrow), filling them to the brim with tasks, and never finish any tasks (a few maybe on a few of his computers)

https://setiweb.ssl.berkeley.edu/beta/hosts_user.php?sort=rpc_time&rev=0&show_all=1&userid=1445

And all the Windows machines are identical in every way, and so are the linux ones, not sure what is going on there or why. Still I suppose all the tasks will time out, eventully

One thought, perhaps school computers that have the disk image replaced every day and it also replaces the BOINC directory so it is seen as new every day.

I counted only 26 computers with a RAC above zero, out of 260 (as of this post) — and of those that had a RAC, many of them were in the 0,07-9 range...

If those are school computers, does he have permission to run BOINC on them? It could be that this guy/gal does not have that permission, and the school IT admin sees the abuse , wipes the disk of WU's, but hasn't figured out who he/she is, or that the Admin needs to delete the BOINC directory...

---

And does much the same on main. The computers come along in batches over a few months, then stop. The pattern has been going on for nearly 12 years.

Agreed, Beta is for testing software — But how are we, the users, going to know if our work for Beta is productive (as in "working", and not producing bad results...) if the stats export is off?

Personally I have never used any of the stats sites. If you crunch on Beta it is much more up to you to check how your machines are performing.

I try and check my results each day to make sure my "Invalid" and "error" count is as close to zero as possible. I also do this on main, that way I know my machines are performing as intended

---

Personally I have never used any of the stats sites. If you crunch on Beta it is much more up to you to check how your machines are performing.

I try and check my results each day to make sure my "Invalid" and "error" count is as close to zero as possible. I also do this on main, that way I know my machines are performing as intended

I use the stats sites to keep an eye on my production Seti, and other BOINC projects - but Beta is shown on them, so I keep track of that, too...

---