geokilla wrote:Ya.... the problem disappeared. I dunno what happened.
And what makes you think I can make the deadline when it took over 2 hours to complete one WU? o.O
Several reasons.
1. I don't happen to know the deadline on 2662
2. I had a random slowdown on my VM client on sunday
3. The fact that you usually generate 1400PPD led me to think that your machine had enough ommph to deal with SMP clients easily
4. I was guessing that you could make the deadline
Anyway glad the problem has gone away but you are not the first person to have this happen and you certainly won't be the last
geokilla wrote:Ya.... the problem disappeared. I dunno what happened.
And what makes you think I can make the deadline when it took over 2 hours to complete one WU? o.O
Several reasons.
1. I don't happen to know the deadline on 2662
2. I had a random slowdown on my VM client on sunday
3. The fact that you usually generate 1400PPD led me to think that your machine had enough ommph to deal with SMP clients easily
4. I was guessing that you could make the deadline
Anyway glad the problem has gone away but you are not the first person to have this happen and you certainly won't be the last
Usually....Drops by half when my sister is using it. Plus it wasn't the first time that I've seen the A2 WU give me about 250PPD. There was lots of WU giving people this problem a while back, but apparently it was fixed. I'm not sure how I got it again earlier, but it's gone now.
SMP WU deadlines aren't long....that's all you need to know =)
Intel Core i5-10600KF @ 4.9Ghz @ 1.25V
MSI Z490 Gaming Edge Wi-Fi BIOS v17
XPG D50 32GB DDR4-3200 16-19-9-36 2T (Samsung M-Die)
XPG S11 Pro 1TB and Western Digital WD140EDFZ 14TB
ASUS TUF RTX 3070 OC
Corsair RM650x
Phantek P360A with Noctua Exhaust Fans
geokilla wrote:There was lots of WU giving people this problem a while back, but apparently it was fixed. I'm not sure how I got it again earlier, but it's gone now.
You've only got half of the story. The WUs that were abnormally slow had the wrong number of steps for a given project. For example, you normally see messages of the form [hh:mm:ss] Completed xxxx out of 250000 steps (yy %). The slow WUs would have some other number much larger than 250000 and those WUs should be reported. (Other projects might have a different number of steps -- the 250000 is correct for project 2662)
Hmm I don't know if it's related to my sister playing MapleStory or not, but I highly doubt it. She couldn't have been playing for over 12 hours straight since this morning. Anyways, the folding has slowed down again. Getting at most 500PPD. Not going to make the deadline now. There was a period of time when she wasn't using the computer for around 2 hours so for sure all of the CPU usage should've went to the Notfred client.
[16:38:29]
[16:38:29] + Processing work unit
[16:38:29] At least 4 processors must be requested.Core required: FahCore_a2.exe
[16:38:29] Core found.
[16:38:29] Working on Unit 01 [January 1 16:38:29]
[16:38:29] + Working ...
[16:38:29]
[16:38:29] *------------------------------*
[16:38:29] Folding@Home Gromacs SMP Core
[16:38:29] Version 2.10 (Sun Aug 30 03:43:28 CEST 2009)
[16:38:29]
[16:38:29] Preparing to commence simulation
[16:38:29] - Ensuring status. Please wait.
[16:38:38] - Assembly optimizations manually forced on.
[16:38:38] - Not checking prior termination.
[16:38:41] - Expanded 4842574 -> 23991465 (decompressed 495.4 percent)
[16:38:41] Called DecompressByteArray: compressed_data_size=4842574 data_size=23991465, decompressed_data_size=23991465 diff=0
[16:38:42] - Digital signature verified
[16:38:42]
[16:38:42] Project: 2669 (Run 4, Clone 77, Gen 189)
[16:38:42]
[16:38:42] Assembly optimizations on if available.
[16:38:42] Entering M.D.
[16:38:48] Using Gromacs checkpoints
[16:38:50] Multi-core optimizations on
[16:39:06] Resuming from checkpoint
[16:39:07] Verified work/wudata_01.log
[16:39:07] Verified work/wudata_01.trr
[16:39:07] Verified work/wudata_01.xtc
[16:39:07] Verified work/wudata_01.edr
[16:39:09] Completed 210010 out of 250000 steps (84%)
[17:45:23] Completed 212500 out of 250000 steps (85%)
[18:45:51] Completed 215000 out of 250000 steps (86%)
[19:53:43] Completed 217500 out of 250000 steps (87%)
[21:08:32] Completed 220000 out of 250000 steps (88%)
Folding@Home Client Shutdown.
--- Opening Log file [January 1 21:18:07]
# SMP Client ##################################################################
###############################################################################
Folding@Home Client Version 6.02
http://folding.stanford.edu
###############################################################################
###############################################################################
Launch directory: /etc/folding/1
Executable: ./fah6
Arguments: -local -forceasm -oneunit -smp 4
Warning:
By using the -forceasm flag, you are overriding
safeguards in the program. If you did not intend to
do this, please restart the program without -forceasm.
If work units are not completing fully (and particularly
if your machine is overclocked), then please discontinue
use of the flag.
[21:18:07] - Ask before connecting: No
[21:18:07] - User name: geokilla (Team 38296)
[21:18:07] - User ID: 79F87C3D43D1822E
[21:18:07] - Machine ID: 1
[21:18:07]
[21:18:07] Loaded queue successfully.
[21:18:07]
[21:18:07] + Processing work unit
[21:18:07] At least 4 processors must be requested.Core required: FahCore_a2.exe
[21:18:07] Core found.
[21:18:07] Working on Unit 01 [January 1 21:18:07]
[21:18:07] + Working ...
[21:18:08]
[21:18:08] *------------------------------*
[21:18:08] Folding@Home Gromacs SMP Core
[21:18:08] Version 2.10 (Sun Aug 30 03:43:28 CEST 2009)
[21:18:08]
[21:18:08] Preparing to commence simulation
[21:18:08] - Ensuring status. Please wait.
[21:18:11] Called DecompressByteArray: compressed_data_size=4842574 data_size=23991465, decompressed_data_size=23991465 diff=0
[21:18:11] - Digital signature verified
[21:18:11]
[21:18:11] Project: 2669 (Run 4, Clone 77, Gen 189)
[21:18:11]
[21:18:11] Assembly optimizations on if available.
[21:18:11] Entering M.D.
[21:18:17] Using Gromacs checkpoints
[21:18:21] M.D.
[21:18:23] core optimizations on
[21:18:27] nts
[21:18:28] Multi-core optimizations on
[21:19:06] Resuming from checkpoint
[21:19:07] Verified work/wudata_01.log
[21:19:08] Verified work/wudata_01.trr
[21:19:08] Verified work/wudata_01.xtc
[21:19:08] Verified work/wudata_01.edr
[21:19:35] Completed 220020 out of 250000 steps (88%)
[22:17:36] Completed 222500 out of 250000 steps (89%)
[23:07:28] Completed 225000 out of 250000 steps (90%)
[00:04:16] Completed 227500 out of 250000 steps (91%)
[01:06:39] Completed 230000 out of 250000 steps (92%)
[02:09:35] Completed 232500 out of 250000 steps (93%)
[03:21:59] Completed 235000 out of 250000 steps (94%)
[04:19:03] Completed 237500 out of 250000 steps (95%)
[05:13:43] Completed 240000 out of 250000 steps (96%)
[06:07:44] Completed 242500 out of 250000 steps (97%)
Intel Core i5-10600KF @ 4.9Ghz @ 1.25V
MSI Z490 Gaming Edge Wi-Fi BIOS v17
XPG D50 32GB DDR4-3200 16-19-9-36 2T (Samsung M-Die)
XPG S11 Pro 1TB and Western Digital WD140EDFZ 14TB
ASUS TUF RTX 3070 OC
Corsair RM650x
Phantek P360A with Noctua Exhaust Fans
Please edit your post to include the entire FahLog from where the WU began to where it ended or post the rest of the run. Then somebody can run FahChart against it and give us a picture of what really happened and when.