41) Message boards : Number crunching : Daily quota (Message 23251)
Posted 25 Sep 2011 by metalius
Post:
haha, funny joke which proves nothing

I am not PROVING something, I am ASKING - if 1 task in progress is not hard (syn. last, extremely etc.) limitation, which limitation is hard then?

Again, you don't understand BOINC scheduling so you cannot understand even the simplest argument about it.

Yeees!!! I don't understand or I stopped to understand, how BOINC scheduling works, especially which kind arithmetic is now used for that. Reality shows - not this arithmetic where 1+1=2 or 2x2=4.

Don't waste your time with examples because I'll just prove them all to be examples of proper scheduling.

Ok, if absolute truth belongs to You, it will belong to You. Amen!
42) Message boards : Number crunching : minor issues with websites (Message 23220)
Posted 23 Sep 2011 by metalius
Post:
Community preferences.
It is impossible to upload avatar (file type - jpg, size - 3.5 kB, 100x100 pixels).
43) Message boards : Number crunching : Daily quota (Message 23216)
Posted 23 Sep 2011 by metalius
Post:
I think at least the previous 3 setting should be tried.

+100! :-) If not 3, then at least 2.
44) Message boards : Number crunching : Daily quota (Message 23211)
Posted 23 Sep 2011 by metalius
Post:
This is not a hard limitation.

Which limitation is hard then? Zero tasks in progress? :-)

It will not slow down this project. It will not affect how many Sixtrack tasks you run over the long term. That is determined by your resource shares.

This time, Your conclusion is too fast and without enough arguments, sorry. Also, resource share is not a panacea. It newer worked properly and especially - it is working absolutely crazy in the newest BOINC versions (later than 6.2.19). I will try too explain this later (on examples).
45) Message boards : Number crunching : Daily quota (Message 23207)
Posted 23 Sep 2011 by metalius
Post:
Right now the limits are as follows:

<max_wus_in_progress> 1 </max_wus_in_progress>

Please, monitor and see how this works.


RU
Ограничение, равное 1 заданию в прогрессе на ядро - это тормоза! Для любого из нас - без всякого сомнения, для проекта в целом - скорее всего тоже.
Почему?
1. После завершения задания неизбежна пауза для отправки результата - в этот момент освободившееся ядро захватывается другим проектом.
2. Выполненное задание некоторое время неизбежно остаётся в статусе "Ожидается подтверждение". В зависимости от версии BOINC такой статус может затянуться до суток - вроде бы.
3. Когда новое задание наконец получено, расчёт не начнётся сразу (ядро уже захвачено другим проектом).
Просьба - увеличьте ограничение на максимум заданий в прогрессе до 2 или хотя бы объясните вашу мотивацию, почему вы прибегли к столь крайне жёсткому ограничению.
-Edit-
Что бы снизить потери времени до минимума, можно, конечно, пока есть работа у LHC@home, остановить все остальные проекты. Но в таком случаи мы вынуждены пасти свои компики, так как в случаи "пустых" (назовём так) заданий дневную квоту компик высосет за несколько минут и потом будет отдыхать до очередного вмешательства пользователя, что абсолютно не приемлемо.
EN
Limitation, equal to maximum 1 task in progress pro core, will slow down the progress for every of us (here is no doubt), and, maybe, for the whole project.
Why?
1. After the task is completed BOINC needs some time to upload the result - in this moment the free core is captured by another project.
2. Completed task remains in the status "Ready to report" for some time too (depending on the version of BOINC that status may take up to 24 hours - not sure here).
3. When a new task is finally received, the processing does not start immediately (the core is working for another project).
Please...
Increase the limit on the maximum of tasks in progress to 2, or at least explain your motivation, why you have decided to use such extremely hard limitation.
46) Message boards : Number crunching : Daily quota (Message 23184)
Posted 21 Sep 2011 by metalius
Post:
Nawiedzony,
You are right, but this is our job here - our hosts must do simulations until correct parameters for shooting will be found. :-)
Possible solution…
Let's ask the project team to increase daily quota!
We have already very important and useful for the project limitation - limited amount of tasks in progress. By this limitation there is no possibility for some undecided participants to download hundreds of tasks and, for example, uninstall BOINC after that. IMHO, daily quota is an extra-limitation now and may be set to formal (big) value.
47) Message boards : Number crunching : Credit awarded calculation (Message 23183)
Posted 21 Sep 2011 by metalius
Post:
Please, monitor and tell us if the change is visible and if it is indeed the right method.

RU
Такой метод с одной стороны приветствуется, но с другой - появляется опасность читерских атак. Обрабатывая последние пакеты из Лондона, я столкнулся с фактами особенно грязной игры, когда компьютер некого анонима запрашивал приблизительно в 100 раз завышенные кредиты, т.е. я заметил, что вместо где-то 5 кредитов оба компьютера (читерский и мой) получили по 250. Раз такое было, значит, может повториться и в результате привести к хаосу в статистике проекта.
EN
This method is welcome, but it may provoke cheating. I saw here some hosts (of anonymous participants, of course) claiming enormous credits. After several successful attacks the cheaters may strike again.
48) Message boards : Number crunching : Daily quota (Message 23181)
Posted 21 Sep 2011 by metalius
Post:
I think something is wrong in the current batch the WUs are estimated to run 8 hours, but terminate only within seconds ...

If current input parameters of the simulation are giving unstable trajectories of the particle beam (the beam will hit something inside of LHC), there is no reason to continue this simulation - the task is finished. So this batch may be Ok with high probability.
49) Message boards : Number crunching : Server unavailable Tuesday 20/9 13:30 CET (Message 23171)
Posted 21 Sep 2011 by metalius
Post:
Which hosts are ok and which have trouble by client version, is it a particular version client with the error ?

Hosts Ok - from 6.2.19 to 6.12.33.
Hosts not Ok - 6.2.19 and 6.10.18.
Upload problem disappears after restarting of BOINC.
50) Message boards : Number crunching : Server unavailable Tuesday 20/9 13:30 CET (Message 23169)
Posted 21 Sep 2011 by metalius
Post:
jujube!
OS reboot helps!
It looks like - You know all here... :-)
Thank You very much!
51) Message boards : Number crunching : Server unavailable Tuesday 20/9 13:30 CET (Message 23168)
Posted 21 Sep 2011 by metalius
Post:
Did you put http://lhcathomeclassic.cern.ch/sixtrack_cgi/file_upload_handler in a browser on the machines that cannot upload?

Yes!
Have you tried rebooting the OS?

No! But I will try right now. Thank You!
52) Message boards : Number crunching : Server unavailable Tuesday 20/9 13:30 CET (Message 23166)
Posted 21 Sep 2011 by metalius
Post:
Try the following URL in your browser and see what you get:
http://lhcathomeclassic.cern.ch/sixtrack_cgi/file_upload_handler
I get:
<data_server_reply>
    <status>1</status>
    <message>no command</message>
</data_server_reply>

I get the same, but several (NOT ALL) hosts can not upload!
I see connect() failed again and again.
Panic mode is on.
53) Message boards : Number crunching : Server unavailable Tuesday 20/9 13:30 CET (Message 23164)
Posted 21 Sep 2011 by metalius
Post:
I can not upload too.
Server status shows OK for all of processes, but I got messages:
21/09/2011 07:36:24 | LHC@home 1.0 | Temporarily failed upload of w3_weak3_collision_err_bb__19__s__64.31_59.32__6_8__6__54_1_sixvf_boinc184871_0_0: connect() failed
21/09/2011 07:36:24 | LHC@home 1.0 | Backing off 11 min 32 sec on upload of w3_weak3_collision_err_bb__19__s__64.31_59.32__6_8__6__54_1_sixvf_boinc184871_0_0
21/09/2011 07:36:26 | | Internet access OK - project servers may be temporarily down.
54) Message boards : Number crunching : No start tag! (Message 23021)
Posted 15 Sep 2011 by metalius
Post:
Hello!

15/09/2011 11:12:59 | LHC@home 1.0 | Reporting 1 completed tasks, requesting new tasks for GPU
15/09/2011 11:13:04 | LHC@home 1.0 | Scheduler request completed: got 0 new tasks
15/09/2011 11:13:04 | LHC@home 1.0 | Message from server: Error in request message: no start tag


Can somebody explain, what is going wrong?

Thank You... :-)
55) Message boards : Number crunching : Sixtrack project temporarily unavailable Wed 14 Sept (Message 23020)
Posted 15 Sep 2011 by metalius
Post:
Welcome back! :-)
56) Message boards : Number crunching : Status of LHC@home (Message 23001)
Posted 12 Sep 2011 by metalius
Post:
And the server status page is restricted to admins, not for all to see, so we don't even know what's down...

Dear project team!
It is very useful for us to see Server status page, but it is hidden now. Why?
57) Message boards : Number crunching : A lot of mismatching results! (Message 22951)
Posted 8 Sep 2011 by metalius
Post:
Update.
My hosts started to produce Invalid results.
Situation looks like:
1. validator is marking as Invalid all 3rd results after situation "Validation inconclusive";
2. WU is closed with canonical result (_0 or _1) after that.
Please, fix it (if I am right).
58) Message boards : Number crunching : A lot of mismatching results! (Message 22941)
Posted 7 Sep 2011 by metalius
Post:
Update:
34 - validated;
28 - no consensus.
Success rate is approaching to 1/2.
My prognosis - in the next few hours validator will stop at all.
Happy crunching! :-D
59) Message boards : Number crunching : A lot of mismatching results! (Message 22930)
Posted 7 Sep 2011 by metalius
Post:
Hello!

Looking to current validation of my results, the situation for LHC@home is never seen before:
30 results - validated;
8 - validation inconclusive.
So, success rate is less than 4/5!

Regards!
60) Message boards : Number crunching : Why is project asking for jobs for GPU (Message 22744)
Posted 1 May 2011 by metalius
Post:
How do I get this fixed?

Upgrade BOINC manager to newest versions or go back to old, which know nothing about GPU.


Previous 20 · Next 20


©2024 CERN