| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 315
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Is doubling the checkpoints to every 3 simulated hours feasible? Very few people seem to understand that the data analyzed is not from a 6-hours period, but the the data of one fixed time e.g. 06:00 UTC or 12:00 UTC and not the period from 06 to 12. So check-pointing more often will be very hard or one have to run this on a virtual machine where one could make snapshots more often during the analyzing process. I don't believe that's true based on what I was seeing in the output while the WU was running for the 3 domains. It is simulating a 48 hour period but checkpointing every 6 hours. I don't have one running right now to pull the output. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
i386 architecture will be dropped starting with eoan (Ubuntu 19.10). I think they are dropping 32bit support which I assume also includes i686 although haven't seen any definitive statement on that. i386 and i686 (generally written as x86 by techs) are basically versions of the 32bit CPU architecture - i386 refers to the instruction set found in the Intel 386 series (386sx25, 386dx2-66, etc.), i686 refers to the enhanced instruction set starting with Pentium Pro (5 second overview, it's more complicated than that - hit up Wikipedia). Various other Linux distros have already dropped 32bit support (RHEL / CentOS 7 for example), it's been on it's way out for a long time. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
So what does that mean for these:
-----------------------------------------rwxr-xr-x 1 boinc boinc 1618326 Jan 23 06:20 wcgrid_hst1_gfx_7.26_i686-pc-linux-gnu -rwxr-xr-x 1 boinc boinc 31340476 Jan 23 06:21 wcgrid_hst1_gromacs_7.26_i686-pc-linux-gnu -rwxr-xr-x 1 boinc boinc 718324 Jan 9 18:15 wcgrid_mcm1_gfx_7.43_i686-pc-linux-gnu -rwxr-xr-x 1 boinc boinc 2446068 Jan 9 18:15 wcgrid_mcm1_map_7.43_i686-pc-linux-gnu -rwxr-xr-x 1 boinc boinc 779764 Sep 16 2018 wcgrid_oet1_gfx_7.23_i686-pc-linux-gnu -rwxr-xr-x 1 boinc boinc 2790144 Sep 16 2018 wcgrid_oet1_vina_7.23_i686-pc-linux-gnu -rwxr-xr-x 1 boinc boinc 1653452 Nov 3 2018 wcgrid_scc1_gfx_7.08_i686-pc-linux-gnu [Edit 1 times, last edit by Doneske at Jun 19, 2019 11:15:43 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Is doubling the checkpoints to every 3 simulated hours feasible? Very few people seem to understand that the data analyzed is not from a 6-hours period, but the the data of one fixed time e.g. 06:00 UTC or 12:00 UTC and not the period from 06 to 12. So check-pointing more often will be very hard or one have to run this on a virtual machine where one could make snapshots more often during the analyzing process. I don't believe that's true based on what I was seeing in the output while the WU was running for the 3 domains. It is simulating a 48 hour period but checkpointing every 6 hours. I don't have one running right now to pull the output. Did not understand the CP answer, but earlier it was explained by one of the techs that it let's say, the weather/climate data analysis standard... measurements are offered of data points taken every 6 hours. Besides not looking for 1gig of data being intermediately stored in hopes the model can be reloaded without bites going the wrong way. Already my machine is sweating with limiting it by 1 at the time. Last upload took so long, there were 4 other tasks results backed up by the time the upload was finished. [Edit 1 times, last edit by Former Member at Jun 20, 2019 12:06:24 AM] |
||
|
|
hchc
Veteran Cruncher USA Joined: Aug 15, 2006 Post Count: 865 Status: Offline Project Badges:
|
The BOINC client's default transfer limit per project (e.g. WCG) is 2 transfers at a time and 8 transfers at a time total. I wonder if manually increasing this would help with the congestion.
----------------------------------------
|
||
|
|
JSYKES
Senior Cruncher Joined: Apr 28, 2007 Post Count: 206 Status: Offline Project Badges:
|
An update to my last post - the previously mentioned beta-ARP WU is now at 65% after 25hrs (it's running on an 8 thread chip) with dozens of ordinary Openzika's and beta-SCC's passing it by and processing to successful conclusion in the meantime!! The prediction is for a further 13hrs of crunching time.... and that's on a 24/7 machine with 12GB of RAM...
----------------------------------------I'm not sure that I would want more than one ARP WU running at a time...or am I being pessimistic about the potential resource requirements of these WU's? ![]() |
||
|
|
hchc
Veteran Cruncher USA Joined: Aug 15, 2006 Post Count: 865 Status: Offline Project Badges:
|
Maybe it demands a lot of L3 cache?
----------------------------------------
|
||
|
|
Jean-David Beyer
Senior Cruncher USA Joined: Oct 2, 2007 Post Count: 339 Status: Offline Project Badges:
|
I have RHEL6.10 running on a 64-bit machine. Therefore, I get mostly x86_64 programs to run. However my ClimatePrediction stuff is all x86 stuff (although x86_64 programs will be coming out in the future).
----------------------------------------For WCG stuff, I have some programs still lying around and, as far as I know, they have all worked. Here are a few. wcgrid_beta11_7.00_i686-pc-linux-gnu: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, for GNU/Linux 2.2.5, stripped wcgrid_beta11_qchemB_prod_linux.x86.7.00: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, for GNU/Linux 2.2.5, stripped wcgrid_beta17_7.36_i686-pc-linux-gnu: ELF 32-bit LSB executable, Intel 80386, version 1 (GNU/Linux), statically linked, for GNU/Linux 2.6.18, stripped wcgrid_beta17_gfx_7.43_x86_64-pc-linux-gnu: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, stripped wcgrid_beta17_map_7.43_x86_64-pc-linux-gnu: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), statically linked, for GNU/Linux 2.6.32, stripped wcgrid_beta19_7.21_x86_64-pc-linux-gnu: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), statically linked, for GNU/Linux 2.6.18, stripped Note that the 32-bit ones were statically-linked, so it does not matter what libraries my machine has. It happens that I have the compatibility library for the C++ stuff, but it is not always used. On the other hand, it appears that compatibility libraries are no longer required. Here is a ClimatePrediction example: $ ldd hadam4_8.09_i686-pc-linux-gnu linux-gate.so.1 => (0x00ba9000) libpthread.so.0 => /lib/libpthread.so.0 (0x007c3000) libdl.so.2 => /lib/libdl.so.2 (0x007eb000) libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00c44000) libm.so.6 => /lib/libm.so.6 (0x00aaf000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x0013b000) libc.so.6 => /lib/libc.so.6 (0x0062a000) /lib/ld-linux.so.2 (0x56617000) $ ls -l /usr/lib/libstdc++.so.6 Jun 19 2018 /usr/lib/libstdc++.so.6 -> libstdc++.so.6.0.13 $ rpm -qf /usr/lib/libstdc++.so.6 libstdc++-4.4.7-23.el6.i686 $ rpm -qf /usr/lib/libstdc++.so.6.0.13 libstdc++-4.4.7-23.el6.i686 On my machine, the compatibility library is $rpm -qf libstdc++-3-libc6.2-2-2.10.0.so compat-libstdc++-296-2.96-144.el6.i686 And it does not seem to be needed anymore, at least for ClimatePrediction programs. ![]() |
||
|
|
Pete Broad
Senior Cruncher Wales Joined: Jan 3, 2007 Post Count: 169 Status: Offline Project Badges:
|
I've had around 80-90 units on my Androids. No errors so far, however I'm seeing a few stuck on 0% but a reboot seems to kick them back to life.
----------------------------------------O.K, 36 Valid, 36, Awaiting validation, 34, in progress. No errors, no out of time units, look to be taking anything from 6 to 14 hours to complete. Pete ![]() [Edit 1 times, last edit by Pete Broad at Jun 20, 2019 7:58:01 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Would it be helpful to change the title of this thread to make it clear that this is for the ARP1 beta?
|
||
|
|
|