There is going to be a big maintenance on 11.09.2017. It will take nearly 5 - 7 days. Servers won't be processing any work during maintanenace and most of the time might be offline.

Radim Vančo (FoxKyong)

ale neee!

Thanks for the heads up about the upcoming maintanenace Kyong.

---

Hobbies...Visual astronomy and astro imaging

ale joooo! :-)
Thanx, Kyong! Stacking up on full 10 days worth of Asteroids WUs !

P.S.
But please, why doesn't the project automatically send AVX WUs to Ryzen CPUs?? Please, check my host "BRISINGR-II" - http://asteroidsathome.net/boinc/show_host_detail.php?hostid=444059 - he has got just many many many sse3 tasks only - for reasons unknown! ... They (AVX) really run a lot faster on ZEN-architecture AMDs (tested) than sse3 (eventhough they sure DO generate a bit of extra heat... approx. +10 Watts).

Thanx (anyone) in advance for any explanation on what might be the cause of this mystery... :-)

---

Melwen - child of the Fangorn Forest

ok...

It is likely that the scheduling server is programmed for Bulldozer family CPUs when it sees AMD, because AVX is slower than SSE3 on AMD Bulldozer and Piledriver CPUs.

Yes. Exactly. Good point.

As my observations reveal, it probably expects sse2/sse3 to be faster, sending it (to AMD CPUs) FIRST. But as the PC computes cca 600 WUs, it will try sending another 600 of AVX to fairly measure the effective throughput in GIGAFlops (visible on the page with application statistics for the host). So, when the host computed cca six hundred WUs of sse2, the server finally has started to send it AVX WUs. But the statistics does NOT look well for the AVX, because this host has always had some ISSUE with CPU cooling (despite huge 150W cooler Pure Rock). AVX2 generates MORE heat which throttles (or used to throttle - before the problem was partially solved) the CPU clocks down + it takes more CPU resources, making the "Multi-Threading" less effective! So, sse2 wins (it seems), but it is really close. But after I will upgrade cooling to water... AVX2 will win :-)

Edit: OK, AVX is already winning. Because the cooling is better now.

BRISINGR-II application details:
http://asteroidsathome.net/boinc/host_app_versions.php?hostid=444059

---

Melwen - child of the Fangorn Forest

There is going to be a big maintenance on 11.09.2017. It will take nearly 5 - 7 days. Servers won't be processing any work during maintanenace and most of the time might be offline.

Radim Vančo (FoxKyong)

Is that November 9th or September 11th? Depends on whether you are American or European on how you read the numbers.

September 11th, work/change is already in process.
BG

What`s about the WU with Deadline 17 September? I ended a lot of those now...

hopefully Kyong sets the server settings to accept every WU that has a deadline after starting the server maintainance yesterday, everybody could be affected according how long maintainance will take. thx

I currently have 31 w/u`s that are completed and awaiting upload with a deadline of the 14th, plus several w/u`s for the 15th, so hoping Kyong will adjust the necessary deadline dates for these to be accepted.

---

Hobbies...Visual astronomy and astro imaging

hopefully Kyong sets the server settings to accept every WU that has a deadline after starting the server maintainance yesterday, everybody could be affected according how long maintainance will take. thx

OK thanks ;-)

Hehe, I currently have cca 160 WUs completed...
and every day about 110 new avx-WUs are completed on my Ryzen 1800X ;)

I currently have 31 w/u`s that are completed and awaiting upload with a deadline of the 14th, plus several w/u`s for the 15th, so hoping Kyong will adjust the necessary deadline dates for these to be accepted.

---

Melwen - child of the Fangorn Forest

Me too!

I remember having read once, maybe for another project, that it is technically impossible to change the deadline after the WUs are sent out. What Kyong could do, is suspending the validator for the first 24 hours. Only fresh WUs would be sent out in the beginning. This would give us all a full day to report our work and prevent the system from issuing replacement units. We would get credit for our useful work and no replacement units would be wasted (3 units reported for a quorum of 2).

Good point!

Me too!

I remember having read once, maybe for another project, that it is technically impossible to change the deadline after the WUs are sent out. What Kyong could do, is suspending the validator for the first 24 hours. Only fresh WUs would be sent out in the beginning. This would give us all a full day to report our work and prevent the system from issuing replacement units. We would get credit for our useful work and no replacement units would be wasted (3 units reported for a quorum of 2).

---

Melwen - child of the Fangorn Forest

Upload/Download server is still runing so if you upload your work till deadline validator should accept it.

Ahh, very good :) Thx Kyong.

Upload/Download server is still runing so if you upload your work till deadline validator should accept it.

Confused.com, all my completed w/u`s are stating ready to report, but have not uploaded from my computer, so will they be accepted when the maintenance is completed, given my deadline date starts from the 14th and dates later than that.

In other words, if the download and upload servers are still running why are the completed w/u`s still on my computer?

---

Hobbies...Visual astronomy and astro imaging

My systems are uploading the WUs to the server, you can check this in the messages (eventlog) Boinc says "Started upload of Workunit xyz" and "Finished Upload of Workunit xyz".
I've read this in the seti forum:

The Transfer tab shows details in real time when something is actually downloading or uploading. At other times it is empty.

All downloads and upload action is logged in the Messages tab.

The upload process in BOINC is twofold.
1. it uploads the data you crunched to a place on the server.
2. it reports the task to the science database.

As it looks, you may have uploaded, but not reported yet. Reporting of tasks happens:
1) 24 hours after completion (was Connect every X after completion).
2) 24 hours before report is due.
3) Connect every X before report is due.
4) On a trickle up message (CPDN only so far).
5) On a request for more work.
6) On a manual update. (Projects tab, select Seti, click Update)

if this is correct/up to date, it's ok that the tasks stay at the client too, because reporting to the database is off.