p6013 R0 C160 G98
Posted: Thu Jun 17, 2010 11:51 am
One of my dual-cores had this unfortunate assignment. With an expected completion time of 107 hours versus a 72-hour hard deadline, I had to delete it. What's with the rash of Run-0 6013's that take almost as long as bigadv units?
Code: Select all
[08:33:38] - Connecting to assignment server
[08:33:39] - Successful: assigned to (130.237.232.140).
[08:33:39] + News From Folding@Home: Welcome to Folding@Home
[08:33:39] Loaded queue successfully.
[08:33:49] + Closed connections
[08:33:49]
[08:33:49] + Processing work unit
[08:33:49] Core required: FahCore_a3.exe
[08:33:49] Core found.
[08:33:49] Working on queue slot 04 [June 17 08:33:49 UTC]
[08:33:49] + Working ...
[08:33:49]
[08:33:49] *------------------------------*
[08:33:49] Folding@Home Gromacs SMP Core
[08:33:49] Version 2.19 (Mar 12, 2010)
[08:33:49]
[08:33:49] Preparing to commence simulation
[08:33:49] - Assembly optimizations manually forced on.
[08:33:49] - Not checking prior termination.
[08:33:50] - Expanded 979403 -> 10427873 (decompressed 1064.7 percent)
[08:33:50] Called DecompressByteArray: compressed_data_size=979403 data_size=10427873, decompressed_data_size=10427873 diff=0
[08:33:50] - Digital signature verified
[08:33:50]
[08:33:50] Project: 6013 (Run 0, Clone 160, Gen 98)
[08:33:50]
[08:33:50] Assembly optimizations on if available.
[08:33:50] Entering M.D.
[08:34:13] Completed 0 out of 250000 steps (0%)
[09:38:30] Completed 2500 out of 250000 steps (1%)
[10:42:23] Completed 5000 out of 250000 steps (2%)