https://boinc.progger.info/odlk/

Be prepared for 3 times or greater than normal task production.

Be prepared for 3 times or greater than normal task production.

Thanks for the info.

Some graphs to demonstrate the load:



btw these graphs are auto updating

See
https://boincstats.com/en/stats/177/project/detail/credit

The project is announced 1 day prior to actual event start. So people download a bunch of work and credit will be submitted during this time period: 09/27/2018 21:00 (UTC) - 09/30/2018 20:59 (UTC) Watch for the credit jump then.

The project is announced 1 day prior to actual event start. So people download a bunch of work and credit will be submitted during this time period: 09/27/2018 21:00 (UTC) - 09/30/2018 20:59 (UTC) Watch for the credit jump then.

Yes, I specifically published statistics before the start of the Sprint.

---

My new article "SOLS and SODLS"
in Russian https://yadi.sk/d/nvdI6TgBrKv72A
in English https://yadi.sk/d/VeY9bx6_q6CcZg

Appears the project can't handle it. Everything stopped working about 2 minutes after the hour the Sprint officially started.

I think the FB page missed the 1st update due to ODLK server's slowness.

Appears the project can't handle it. Everything stopped working about 2 minutes after the hour the Sprint officially started.

About me, Sprint in progress

1 SETI.USA 25 97,148
2 BOINC@AUSTRALIA 18 49,346
3 Russia Team 15 34,291
4 TeAm AnandTech 12 30,042
5 Czech National Team 10 18,498
6 Rechenkraft.net 8 7,375
7 Overclock.net 6 5,324
8 UK BOINC Team 4 4,996
9 L'Alliance Francophone 2 1,819
10 The Knights Who Say Ni! 1 1,671
11 Planet 3DNow! - 1,386
12 The Planetary Society - 672
13 Gridcoin - 658
14 BOINC@Poland - 147
15 SETI.Germany - 86
16 SETIKAH@KOREA - 23
0 Team China - 0
0 BOINC.Italy - 0
0 USA - 0
0 Boinc@Taiwan - 0
0 Dutch Power Cows - 0
0 Ukraine - 0
0 OcUK - Overclockers UK - 0

See
http://formula-boinc.org/sprint.py?sprint=16&lang=ru&year=2018

Yes, the project runs on a home server.

Perhaps, the organizers of Sprint should first discuss this issue with the project administrator.

---

My new article "SOLS and SODLS"
in Russian https://yadi.sk/d/nvdI6TgBrKv72A
in English https://yadi.sk/d/VeY9bx6_q6CcZg

The feeder server appears to have stopped running.

Dear participants!

Please keep calm.

If the ODLK project server can not cope with the increased load, it is not the fault of the project administrator.

Did the Sprint organizers discuss the issue with the project administrator?
We already had a similar problem in the ODLK1 project when this project participated in the Sprint.
See
https://boinc.multi-pool.info/latinsquares/forum_thread.php?id=39

So what you're saying is you couldn't careless about our free help? Cool.

So what you're saying is you couldn't careless about our free help? Cool.

I personally think that statement is unfair to say. I will guess the project appreciates the help we are giving them.

If their server is adequate for 362 of 365 days out of a year. Why should ODLK upgrade? I can see it from their side. Yeah if it was upgraded they could capture a significant quantity of WUs completed, but evidently they've decided they are OK with the rate of work returned on a normal day.

If Formula Boinc properly review their Sprint project candidates we wouldn't even be in this situation, since this project would never have made it on the Sprint list since ODLK's infrastructure doesn't support these very large spikes in load.

Regarding inclusion of ODLK as a sprint project, there was a discussion in December 2017 on which projects to make candidates for 2018 sprints:
http://formula-boinc.org/forum/viewtopic.php?f=14&t=100

This was when ODLK and ODLK1 were added, among others. I don't know whether the Formula Boinc admin Sebastien or anybody else approached the respective admins during this discussion.

Regarding preparation for any individual sprint, Sebastien once stated that while the project of an upcoming sprint is selected at random, he performs some manual checks before the sprint announcement. However, my understanding is that Sebastien never contacts the project admins.

--------
H|Skillz wrote:

So what you're saying is you couldn't careless about our free help? Cool.

No, what @Natalia Makarova was saying is that the project is run on a home server.

Meanwhile, it seems @Progger took care of the server very early in the morning. Feeder, validators, work generators etc. were down soon after the beginning of the sprint, but they are all running now.

There continue to be HTTP timeouts, but at least all server functions appear to be working.

You can say that, but some project administrators took the initiative to optimize their servers to handle our free help as demonstrated here.

http://rake.boincfast.ru/rakesearch/forum_thread.php?id=101#485

So if the project administrators here aren't going to be proactive about our participation then perhaps we shouldn't include them anymore.

No, what @Natalia Makarova was saying is that the project is run on a home server.

Meanwhile, it seems @Progger took care of the server very early in the morning. Feeder, validators, work generators etc. were down soon after the beginning of the sprint, but they are all running now.

There continue to be HTTP timeouts, but at least all server functions appear to be working.

Thank you.

I personally think that statement is unfair to say. I will guess the project appreciates the help we are giving them.

If their server is adequate for 362 of 365 days out of a year. Why should ODLK upgrade? I can see it from their side. Yeah if it was upgraded they could capture a significant quantity of WUs completed, but evidently they've decided they are OK with the rate of work returned on a normal day.

If Formula Boinc properly review their Sprint project candidates we wouldn't even be in this situation, since this project would never have made it on the Sprint list since ODLK's infrastructure doesn't support these very large spikes in load.

Thank you.

---

My new article "SOLS and SODLS"
in Russian https://yadi.sk/d/nvdI6TgBrKv72A
in English https://yadi.sk/d/VeY9bx6_q6CcZg

[H]Skillz,
I assume that the admin isn't a robot, and that he lives in the UTC+03:00 time zone. This puts the start of the sprint at midnight local time. Not a perfect time for being proactive. (And maybe the admin even has a day job to attend to or something. Actually, most DC project admins do.)

I think that the following things would help:
1. prolonging time for http gateway
2. prolonging time for contacting ODLK server from our hosts to about 2-5 minutes.

because:
little number of ready workunits is accepting in about 10 seconds, but 1000+ need more time for accepting wu´s.
Godd luck.

Longer tasks = fewer connections. My 1950x is completing nearly 2 tasks every minute. Upload, acknowledge, report, acknowledge, download, acknowledge. Assimilate, validate, etc, etc. Twice per work unit.



350k to 1.2m jump and tomorrows update will be much more yet still limited by the server. If this was run at home an ISP would probably cut the connection thinking it was spam from the increased volume.