Posts by JagDoc

1) Message boards : Number crunching : Credit Award Consistency? (Message 1974)
Posted 30 Jan 2023 by JagDoc
Post:
For granting a fair credit to a computer, BOINC server must have a fair benchmark and have gathered appropriate statistics based on the set of tasks completed on this computer.
You can look, for instance, at my computer (# 4). Credits awarded per hour do not vary much because it has relatively large statistics of computing with cmdock-l 2.02 application version. This illustrates what value of granted credit is fair, too.

The Boinc benchmark is not fair/correct.
With Linux 20.x and higher you get the best benchmark value.
With Linux 18.x it is lower.
With Windows it is much lower.
2) Message boards : Number crunching : Credit Award Consistency? (Message 1968)
Posted 30 Jan 2023 by JagDoc
Post:
Here the wright links for the results:
https://www.sidock.si/sidock/result.php?resultid=77673401
https://www.sidock.si/sidock/result.php?resultid=77686084
3) Message boards : Number crunching : Credit Award Consistency? (Message 1965)
Posted 29 Jan 2023 by JagDoc
Post:
On one of my hosts Credit dropped from 955.43Cr to 390.61Cr , same runtime :
https://www.sidock.si/sidock/result.php?resultid=77686084
https://www.sidock.si/sidock/result.php?resultid=77686084

Is there a reason for that.

Hi!
Very unusual results! How many cores of this CPU used for computing? Could you run benchmark over used cores and post the result? And what frequency of CPU cores during computing?
Thank you!

The host is running headless only Boinc controlled with BoincTasks. I have run the benchmark after installation.
All 8C/8T running Boinc. 2 x Sidock, 4 x NFS, 1 x iThenaComp and 1 x Climate , frequency 2,44GHz at full load.
4) Message boards : Number crunching : Credit Award Consistency? (Message 1960)
Posted 29 Jan 2023 by JagDoc
Post:
On one of my hosts Credit dropped from 955.43Cr to 390.61Cr , same runtime :
https://www.sidock.si/sidock/result.php?resultid=77686084
https://www.sidock.si/sidock/result.php?resultid=77686084

Is there a reason for that.
5) Message boards : Number crunching : Eprot_v1 end with error on ARM (Message 1202)
Posted 18 Sep 2021 by JagDoc
Post:
This must be wrong settings in the wu.
Boinc shows on Eprot_v1 and 3CLpro wu the same estimated runtime.
6) Message boards : Number crunching : Eprot_v1 end with error on ARM (Message 1200)
Posted 18 Sep 2021 by JagDoc
Post:
New WUs also ended with this error.

My 2400GE has the same problem with Eprot_v1 wu.
https://www.sidock.si/sidock/result.php?resultid=20168126

From where takes the app this value?
If you look in the resultid there is max. FLOPS des Gerätes 5.10 GFLOPS
and in the stderr: exceeded elapsed time limit 39481.06 (1000000.00G/25.30G)

Some of my team mates has the same Problem.
Please stop sending out Eprot_v1 untill problem is solved.
7) Message boards : News : SiDock@home September Sailing (Message 1194)
Posted 17 Sep 2021 by JagDoc
Post:
Something is wrong, all wu after 8:00 are send out only 1 x, no wingman (status unsent)
8) Message boards : Number crunching : Eprot_v1 end with error on ARM (Message 1192)
Posted 17 Sep 2021 by JagDoc
Post:
Thank you.
I aborted on the ARMs the Eprot_v1.
Tomorrow we will se how it works with the new WUs
9) Message boards : Number crunching : Eprot_v1 end with error on ARM (Message 1188)
Posted 17 Sep 2021 by JagDoc
Post:
On all my Odroid-N2 the Eprot_v1 end after 1d3h30m runtime with 197 (0x000000C5) EXIT_TIME_LIMIT_EXCEEDED.

<core_client_version>7.16.6</core_client_version>
<![CDATA[
<message>
exceeded elapsed time limit 99186.72 (1000000.00G/10.08G)</message>
<stderr_txt>
04:31:39 (1302552): wrapper (7.17.26016): starting
04:31:39 (1302552): wrapper (7.17.26016): starting
04:31:39 (1302552): wrapper: running cmdock (-c -r target.prm -p "/var/lib/boinc-client/slots/3/data/scripts/dock.prm" -f htvs.ptc -i ligands.sdf -o docking_out)

</stderr_txt>
]]>


Have you changed the settings? All host run this before without problem.
https://www.sidock.si/sidock/results.php?hostid=12224
10) Message boards : News : Release CmDock v 0.1.3 (Message 988)
Posted 29 May 2021 by JagDoc
Post:
The jump to 100% is on slower ARM systems a problem.
I run with work puffer 0/0 but if it goes to 100% boinc get a new WU that is waiting over 2 days to start and will not finish within deadline and i have to cancel it before it starts.
11) Message boards : Number crunching : No checkpoints? (Message 953)
Posted 23 May 2021 by JagDoc
Post:
With windows7 Boinc dont shows the checkpoints correct:
Projekt	SiDock@home
	
Name	corona_Eprot_v1_nb3di_206123_2_1
	
Anwendung	CurieMarieDock on BOINC + zipped input 2.00
Arbeitspaketname	corona_Eprot_v1_nb3di_206123_2
Status	Aktiv
Erhalten	23.05.2021 00:10:17
Deadline	28.05.2021 00:10:00
Geschätzte Anwendungsgeschwindigkeit	1,63 GFLOPs/sec
Geschätzte Arbeitspaketgröße	50.000 GFLOPs
CPU-Zeit beim letzten Checkpoint	00:09:39
CPU-Zeit	09:00:41
Vergangene Zeit	08:31:45
Geschätzte verbleibende Zeit	04:58:35
Fortschritt	63,153%
Größe des virtuellen Speichers	147,75 MB
Größe des Arbeitspakets im Speicher	151,31 MB
Verzeichnis	slots/2
Prozess-ID	2765056

The docking _log and the docking_out.chk shows 462 and the same ligand name.

On my ARMs with Linux BoincTasks shows the checkpoints correct.
12) Questions and Answers : Unix/Linux : Please provide an app for Raspberry Pi (GNU/Linux / ARM64) (Message 949)
Posted 22 May 2021 by JagDoc
Post:
My Odroid-C4 finished the first 4 tasks.
https://www.sidock.si/sidock/results.php?hostid=17214
Runtimes 2 day +-1h.
13) Questions and Answers : Unix/Linux : Please provide an app for Raspberry Pi (GNU/Linux / ARM64) (Message 944)
Posted 21 May 2021 by JagDoc
Post:
The first tasks with the new app on my Odroid-N2+ finished and validated.
Runtime 1d6h20m.
https://www.sidock.si/sidock/results.php?hostid=11776
14) Questions and Answers : Unix/Linux : Please provide an app for Raspberry Pi (GNU/Linux / ARM64) (Message 932)
Posted 21 May 2021 by JagDoc
Post:
After "sudo apt install libgomp1:armhf" it runs without error

Therefore this library should be bundled inside cmdock's .zip file

The WU that crashed has this error:
cmdock: error while loading shared libraries: libgomp.so.1: cannot open shared object file: No such file or directory

The Odroid-C4 and Odroid-N2 run with Ubuntu 20.04.2 LTS 64bit.
To get boinc with 32bit apps running i need to add-architecture armhf and install some :armhf libs.
15) Questions and Answers : Unix/Linux : Please provide an app for Raspberry Pi (GNU/Linux / ARM64) (Message 927)
Posted 20 May 2021 by JagDoc
Post:
On one of my Odroid-N2 it also run without problem.
After 3h5m the docking_log shows:
**************************************************
RECORD #51
NAME:   ZINC000947187298
RNG seed:                     std::random_device
Numer of docking runs done:   5 (0 errors)
Ligand docking duration:      216.457 second(s)

Average duration per ligand:  218.810 second(s)
Approximately 447 record(s) remaining, will finish Fri May 21 17:35:10 2021

**************************************************
RECORD #52
NAME:   ZINC000947187303
RNG seed:                     std::random_device
Numer of docking runs done:   5 (0 errors)
Ligand docking duration:      218.857 second(s)

**************************************************

Estimated runtime is 1d 6h
16) Questions and Answers : Unix/Linux : Please provide an app for Raspberry Pi (GNU/Linux / ARM64) (Message 926)
Posted 20 May 2021 by JagDoc
Post:
Great.
I run it on my Odroid-C4.
First WU crashed with error.

After "sudo apt install libgomp1:armhf" it runs without error.

**************************************************
RECORD #1
NAME:   ZINC000937180731
RNG seed:                     std::random_device
Numer of docking runs done:   5 (0 errors)
Ligand docking duration:      348.741 second(s)

Average duration per ligand:  348.741 second(s)
Approximately 464 record(s) remaining, will finish Sat May 22 05:26:29 2021

**************************************************
RECORD #2
NAME:   ZINC000937180732
RNG seed:                     std::random_device
Numer of docking runs done:   5 (0 errors)
Ligand docking duration:      425.196 second(s)

**************************************************
RECORD #3
NAME:   ZINC000937180755
RNG seed:                     std::random_device
Numer of docking runs done:   5 (0 errors)
Ligand docking duration:      488.344 second(s)

**************************************************
17) Message boards : News : Third target (corona_PLpro_v2) (Message 479)
Posted 29 Jan 2021 by JagDoc
Post:
One of my host got 35 WUs all are valid.
Other host got 16 WUs all are pending.
And now i get no new work on both.
18) Message boards : Number crunching : Threadripper 3990x stingy scheduler (Message 401)
Posted 12 Jan 2021 by JagDoc
Post:
The limit of 2 WU per core is not the problem.
But with the limit of 128 WU per host it is not possible to run hosts with 128 or more cores efficient at SiDock.
This value should increased.
19) Questions and Answers : Unix/Linux : ARM Linux App (Message 376)
Posted 1 Jan 2021 by JagDoc
Post:
Hi! We are working on it, most likely in a few days we will have it!

Happy New Year!

Great. My Odroid-N2 are waiting for work.
Happy New Year.




©2024 SiDock@home Team