Joined: 9 Mar 15
I have a file working on my 6 CPU system that is a 7 day computation. The due date is 11/19 at 15:30. It's only about 1/2 way through the file - I also have 15 other files pending that range from 3 to 14 hours, all due 11/19... Should I just abort them so they can be reassigned or allow them to run?
At this point, should I even be running N-Body files at all?
Number of cores 6 (max 6)
Number of threads 6 (max 6)
Name AMD FX-6300
Specification AMD FX(tm)-6300 Six-Core Processor
Package Socket AM3+ (942)
Extended CPUID 15.2
Core Stepping OR-C0
Technology 32 nm
TDP Limit 95.0 Watts
Core Speed 1406.4 MHz
Multiplier x Bus Speed 7.0 x 200.9 MHz
Base frequency (cores) 200.9 MHz
Base frequency (ext.) 200.9 MHz
Rated Bus speed 2411.0 MHz
Stock frequency 3500 MHz
Instructions sets MMX (+), SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, SSE4A, x86-64, AMD-V, AES, AVX, XOP, FMA3, FMA4
Microcode Revision 0x6000852
L1 Data cache 6 x 16 KBytes, 4-way set associative, 64-byte line size
L1 Instruction cache 3 x 64 KBytes, 2-way set associative, 64-byte line size
L2 cache 3 x 2048 KBytes, 16-way set associative, 64-byte line size
L3 cache 8 MBytes, 64-way set associative, 64-byte line size
Max CPUID level 0000000Dh
Max CPUID ext. level 8000001Eh
Cache descriptor Level 1, D, 16 KB, 1 thread(s)
Cache descriptor Level 1, I, 64 KB, 2 thread(s)
Cache descriptor Level 2, U, 2 MB, 2 thread(s)
Cache descriptor Level 3, U, 8 MB, 6 thread(s)
FID/VID Control yes
Min FID 7.0x
# of P-States 4
P-State FID 0x19 - VID 0x0A - IDD 17 (20.50x - 1.425 V)
P-State FID 0x16 - VID 0x0E - IDD 17 (19.00x - 1.375 V)
P-State FID 0x13 - VID 0x16 - IDD 12 (17.50x - 1.275 V)
P-State FID 0xFFFFFFFF - VID 0xFFFFFFFF (-1.00x - -1.000 V)
Package Type 0x1
String 1 0x0
String 2 0x0
Base TDP 13 Watts
Boosted P-States 2
Max non-turbo ratio 17.50x
Max turbo ratio 20.50x
Joined: 27 Jul 14
Abort. They will be sent to another host anyway if they haven't started by the deadline.
I don't run CPU work here so I don't know if the run time you're seeing is reasonable or not. In any case you have too much work. I recommend lowering your cache, aka Store at least N days of work (N being a number) to something lower than you have now. I don't like to set it at more than one day especially for new projects. Start raising it after you have returned some valid tasks.
Team USA forum | Team USA page
Always crunching / Always recruiting
Joined: 9 Mar 15
Well, to resolve this issue I have taken my 6 CPU Windows 10 system off of Milky Way and put it back on World Community Grid - however, my Linux 4 CPU system seems to not be having any issues with the Milky Way files so I will leave it there as long as it doesn't suddenly develop any problems...
Joined: 6 Jan 13
Similarly, I’m running 7 CPU’s and since these have been appearing on Milky Way it has killed my system on its overnight processing. I removed Climate Change and SETI and watched 5 MW files waiting in the queue (all with 7 CPU’s) waiting for 1 MW file to finish processing. Typically they start out with an hour or two to run but when checking in the morning they often have 2 days left to run. Nothing finishes on time anymore. I have made changes to the configuration without improving the outcome. The CPU usage is typically 1%.
I have disabled MW and re-enabled Climate Change and immediately the files I had suspended all burst into life and the CPU shot up to 95% which is what I have it set to.
The problem may not be due to MW but BOINC, maybe?
I’m not a techie but I think that some one that is needs to look at it.
If it helps here is a summary of my PC. It’s not exactly slow!!!!
2x 1600Mhz DDR3 8GB memory (16GB total)
GIGABYTE GA-Z97X-SU Motherboard
INTEL i7 4790K Processor
NVIDIA GeForce GTX 970 v388.13 4GB Graphics Card
Meanwhile, MW is on hold until this can be resolved which it appears I am not capable of doing.
©2020 Astroinformatics Group