It could be my "Seti Toaster"

To win a SETI Toaster you need to crunch at least 1 Billion credits. LOL

. . I don't think my current toaster will last that long :(

Stephen

:)

Others hit their record racs in backup projects but I have no backups and my S@H rac has now climbed to its all time high!

After the extra long Tuesday outage last week I seem to have received consistently higher than normal credit from the tasks I have crunched. And also because the server is behind and trying to catch up, I have received credit for more than 24 hours of work per day.

---

We are approaching the "magic" number of 23 MM of WU.

Hope all back to normal soon.

---

So E@H doesn't generate as much "heat"?

GPU projects / apps (I am running) in the order of heat generation:
(i3-4160 3.6GHz, 2x4GB DDR3 1333MHz, RTX2080Ti PCIe3.0x16 RAM@13600MHz)

1.       GPUGrid / Acemd3 (cuda10)              GPU@1700MHz 331W
2.     SETI@home / GPU special app (cuda10.2)   GPU@1875MHz 325W
3. Einstein@home / O2MDF 2.07 GW-OpenCL-NVidia  GPU@1875MHz 295W
4. Einstein@home / FGRPB1G 1.20 OpenCL-NVidia   GPU@1875MHz 293W

The power consumption shown is the peak average power consumption while the task is running.
The long term heat output is the best for GPUGrid, as it's running for 1h41m without significant change in the power consumption.
The SETI@home special app has lower heat output in the long term, as it frequently drops to 95W during the workunit change (can be fixed by using mutex bulid).
Einstein@home also has lower heat output in the long term than 295W, as it drops to ~130W at 99% with ~250W spikes.

---

all data distribution stats on the SSP have been stale for over an hour now. but looking at my systems, it seems like I'm actually getting a consistent stream of work now.

come on forum phantom, work your magic!

---

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

So E@H doesn't generate as much "heat"?

Einstein@home definitely uses less power and generates less heat, at least when compared to the Linux CUDA Special application. I can see in the nvidia-smi output that each card pulls less and the temps drop.

no idea on the power draw for SETI SoG but its probably less than the special app since it's much less optimized.

---

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

Server status values still frozen.

---

Grant
Darwin NT

all data distribution stats on the SSP have been stale for over an hour now

When the top of the page lists an 'as of' time that is hours old and those individual stats too have hours in their 'as of' column, do I have to add those hours together to get the true age of the data or does the page actually update without updating the time stamp at the top but still keeping the 'as of' column fresh?

And then there is the replica database lag. So when the data distribution stats say "as of 2h", Replica is 23.8 hours behind master and the time stamp at the top is half an hour in the past, I guess the numbers actually reflect the situation 2.3 hours ago yesterday!

---

you can trust the "as of" times as being the value "as of" whatever time ago. so those were the values right now say 2 hours ago. you do not add them up, they are independent.

the replica database is a lag value already. telling you how far behind it is. that will usually remain up to day, until it stops updating, then the value of lag is itself lagged when it stops updating. you just wont know if the replica delay is getting better or worse since there is no update. right now, probably still getting worse.

the only value that is current/updating is the master db queries/s

---

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

you can trust the "as of" times as being the value "as of" whatever time ago. so those were the values right now say 2 hours ago. you do not add them up, they are independent.

2 hours ago when the page was updated. But if the timestamp at the top is one hour in the past when I load the page, then 'as of 2h' really means 3 hours ago.

Ssp seems to be updating normally now and replica is almost 27 hours behind! The numbers of wus and results have started shrinking quite a bit faster!

---

With the results out in the field back to over 6 million, I have a feeling they may have reached the number they were looking for. When I went to bed last night it was somewhere around 5.5 million

---

With the results out in the field back to over 6 million, I have a feeling they may have reached the number they were looking for.

The situation is not yet ok. The replica database is still falling behind about 24 minutes per hour. It's now one day, 4 hours and 40 minutes behind.

---

I checked the SSP and as of 21 Jan 2020, 1:40:04 UTC they took the replica off line.

---

I checked the SSP and as of 21 Jan 2020, 1:40:04 UTC they took the replica off line.

See that, wasn't much point to it other than telling us how far it had fallen behind the main database. Maybe it can be synced up offline or something.

---

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

A proud member of the OFA (Old Farts Association)

I guess that they took it off line for tomorrows outage FWIW

---

I guess that they took it off line for tomorrows outage FWIW

I assume it will help the servers recover because I am sure it has an I/O impact on the main database. Anything that can help the servers clear the validations and purge/delete backlogs will be welcome.

---

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

A proud member of the OFA (Old Farts Association)

had a good run for about half the day. now back to no tasks available

---

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

Think the splitters have commandeered the I/O and the schedulers are getting short-changed in responding to work requests.

---

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

A proud member of the OFA (Old Farts Association)

Think the splitters have commandeered the I/O and the schedulers are getting short-changed in responding to work requests.

Or all the stuff that hit the replica before is now bombing the master and commandeering the I/O.

---

We'll see if the splitter eventually throttles down after 1.2M or so. At least the replica is back in sync after being taken offline.

---

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

A proud member of the OFA (Old Farts Association)