36 hour work unit. normal?
Moderators: Site Moderators, FAHC Science Team
36 hour work unit. normal?
Was just looking for confirmation as to whether or not the below is normal.
I am currently running a AMD PII 955 @ 3.6, this is my second work unit (the first was using the non-smp client and was ALOT faster) im just woundering if there is a possibility of a huge work unit or not. like 36 hours is a long time.
I am currently running the GPU3 on the side. Im not 100% sure of switches, because im afraid to close the client to check and look 8 hours work. I ran this over night so the system was otherwise idle during this time.
I am currently running a AMD PII 955 @ 3.6, this is my second work unit (the first was using the non-smp client and was ALOT faster) im just woundering if there is a possibility of a huge work unit or not. like 36 hours is a long time.
I am currently running the GPU3 on the side. Im not 100% sure of switches, because im afraid to close the client to check and look 8 hours work. I ran this over night so the system was otherwise idle during this time.
-
- Site Moderator
- Posts: 6986
- Joined: Wed Dec 23, 2009 9:33 am
- Hardware configuration: V7.6.21 -> Multi-purpose 24/7
Windows 10 64-bit
CPU:2/3/4/6 -> Intel i7-6700K
GPU:1 -> Nvidia GTX 1080 Ti
§
Retired:
2x Nvidia GTX 1070
Nvidia GTX 675M
Nvidia GTX 660 Ti
Nvidia GTX 650 SC
Nvidia GTX 260 896 MB SOC
Nvidia 9600GT 1 GB OC
Nvidia 9500M GS
Nvidia 8800GTS 320 MB
Intel Core i7-860
Intel Core i7-3840QM
Intel i3-3240
Intel Core 2 Duo E8200
Intel Core 2 Duo E6550
Intel Core 2 Duo T8300
Intel Pentium E5500
Intel Pentium E5400 - Location: Land Of The Long White Cloud
- Contact:
Re: 36 hour work unit. normal?
Welcome to the F@H Forum jebusv20,
P6040 is among a few large SMP Projects. The Client is configured with -smp flag and I would advice that you also add -verbosity 9 which will help us during troubleshooting.
P6040 is among a few large SMP Projects. The Client is configured with -smp flag and I would advice that you also add -verbosity 9 which will help us during troubleshooting.
ETA:
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time
Welcome To The F@H Support Forum Ӂ Troubleshooting Bad WUs Ӂ Troubleshooting Server Connectivity Issues
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time
Welcome To The F@H Support Forum Ӂ Troubleshooting Bad WUs Ӂ Troubleshooting Server Connectivity Issues
Re: 36 hour work unit. normal?
sorry, yeah. im EXTREMELY new to this, um... can I close the client and reopen it with the -verbosity 9 flag without loosing the current state of the work unit?
Re: 36 hour work unit. normal?
I think I might be running -bigadv
considering I am only running a quad, would that be bad?
considering I am only running a quad, would that be bad?
Re: 36 hour work unit. normal?
Just ran it again with the -verbosity 9 and -smp switches
was not running -bigadv, I am running advanced methods.
Just looking for a confirmation that my computer isnt 'spinning its wheels'
I was having issues before the SMP client with my cpu sitting at 40%
and now a WU thats taking almost 1 1/2 days to complete?
was not running -bigadv, I am running advanced methods.
Just looking for a confirmation that my computer isnt 'spinning its wheels'
I was having issues before the SMP client with my cpu sitting at 40%
and now a WU thats taking almost 1 1/2 days to complete?
Code: Select all
# Windows SMP Console Edition #################################################
###############################################################################
Folding@Home Client Version 6.34
http://folding.stanford.edu
###############################################################################
###############################################################################
Launch directory: C:\Users\Jebusv20\FAH
Executable: fah6
Arguments: -verbosity 9 -smp
[21:53:07] - Ask before connecting: No
[21:53:07] - User name: jebusv20 (Team 202863)
[21:53:07] - User ID: 4203962853B5E805
[21:53:07] - Machine ID: 1
[21:53:07]
[21:53:07] Loaded queue successfully.
[21:53:07]
[21:53:07] - Autosending finished units... [March 15 21:53:07 UTC]
[21:53:07] Trying to send all finished work units
[21:53:07] + Processing work unit
[21:53:07] + No unsent completed units remaining.
[21:53:07] - Autosend completed
[21:53:07] Core required: FahCore_a3.exe
[21:53:07] Core found.
[21:53:07] Working on queue slot 01 [March 15 21:53:07 UTC]
[21:53:07] + Working ...
[21:53:07] - Calling '.\FahCore_a3.exe -dir work/ -nice 19 -suffix 01 -np 4 -priority 96 -checkpoint 15 -verbose -lifeline 5852 -version 634'
[21:53:07]
[21:53:07] *------------------------------*
[21:53:07] Folding@Home Gromacs SMP Core
[21:53:07] Version 2.27 (Dec. 15, 2010)
[21:53:07]
[21:53:07] Preparing to commence simulation
[21:53:07] - Ensuring status. Please wait.
[21:53:17] - Looking at optimizations...
[21:53:17] - Working with standard loops on this execution.
[21:53:17] - Previous termination of core was improper.
[21:53:17] - Going to use standard loops.
[21:53:17] - Files status OK
[21:53:18] - Expanded 7882938 -> 10126021 (decompressed 128.4 percent)
[21:53:18] Called DecompressByteArray: compressed_data_size=7882938 data_size=10126021, decompressed_data_size=10126021 diff=0
[21:53:18] - Digital signature verified
[21:53:18]
[21:53:18] Project: 6040 (Run 0, Clone 108, Gen 129)
[21:53:18]
[21:53:18] Entering M.D.
[21:53:24] Using Gromacs checkpoints
[21:53:25] Mapping NT from 4 to 4
[21:53:26] Resuming from checkpoint
[21:53:26] Verified work/wudata_01.log
[21:53:26] Verified work/wudata_01.trr
[21:53:26] Verified work/wudata_01.xtc
[21:53:26] Verified work/wudata_01.edr
[21:53:27] Completed 67156 out of 250000 steps (26%)
-
- Posts: 460
- Joined: Sun Dec 02, 2007 10:15 pm
- Location: Michigan
Re: 36 hour work unit. normal?
What is the cpu load now? Everything looks OK in the logs. I'm not near my box that runs SMP, so I can't give you a speed check.
Proud to crash my machines as a Beta Tester!
Re: 36 hour work unit. normal?
cpu load is at 100% and has been at 100% for the past 10 hours now.
-
- Posts: 460
- Joined: Sun Dec 02, 2007 10:15 pm
- Location: Michigan
Re: 36 hour work unit. normal?
I'd say your speed is right. I'll check my box later to verify.
Proud to crash my machines as a Beta Tester!
-
- Posts: 85
- Joined: Fri Feb 13, 2009 12:38 pm
- Hardware configuration: Linux & CPUs
- Location: USA
Re: 36 hour work unit. normal?
That's about normal time for a p6040 or p6041. They are rather large. A p6040 took 1.56 Days on My AMD Quad core.
Re: 36 hour work unit. normal?
can I ask how many points it might be worth?
its not 1 is it
its not 1 is it
Re: 36 hour work unit. normal?
Using the folding calculator here -> http://www.linuxforge.net/bonuscalc2.php
It's about 7K points, or 4600 PPD.
It's about 7K points, or 4600 PPD.
Re: 36 hour work unit. normal?
Topodisc is assuming you're an old-timer. You said this was your second WU so I'll explain further.topodisc wrote:Using the folding calculator here -> http://www.linuxforge.net/bonuscalc2.php
It's about 7K points, or 4600 PPD.
SMP WUs are generally well suited for quads like yours which run 24x7. If you fold part-time, smp may or may not be right for you.
Project 6040 is worth 1395.00 points on completion. it is also eligible for a bonus, depending on whether you're using a passkey that has been qualified or not. With the bonus, it would be worth about 7000 points if it is completed at that speed. Without the bonus, you'll get the 1395 points upon completion.
If you don't have a passkey, get one immediately and start work on completing your first 10 bonus-eligible WUs. You'll start getting the bonus on the eleventh WU.
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.
-
- Posts: 208
- Joined: Wed Dec 12, 2007 8:44 pm
- Hardware configuration: Pentium 4 2.8 GHz, 512MB DDR Ram, 128MB Radeon 9800, Creative Soundblaster Audigy 4 Pro
- Location: Jupiter 6
- Contact:
Re: 36 hour work unit. normal?
Code: Select all
[21:53:17] - Looking at optimizations...
[21:53:17] - Working with standard loops on this execution.
[21:53:17] - Previous termination of core was improper.
[21:53:17] - Going to use standard loops.
-
- Posts: 336
- Joined: Fri Jun 26, 2009 4:34 am
Re: 36 hour work unit. normal?
You may see this warning whenever you close your SMP client. Ctrl-C is the right way to close it and you can ignore it when you are working on SMP work units. The optimization is built into the SMP client.
-
- Posts: 450
- Joined: Tue Dec 04, 2007 8:36 pm
Re: 36 hour work unit. normal?
Ctrl-C is the right way to close any client, including SMP. If it's shut down normally you won't get that message Optimizations are always on, so you can ignore the message as is a leftover from an earlier time. It's appropriate to have some concern, though, because when you fail to shut down normally, the chance of encountering a corrupt checkpoint is increased. Though it's unlikely, you really don't want to have the client restart the WU from the beginning and discard the work you've done on it