I didn't mean you with the "no bunkering" hint. I mainly meant @StefanR5R. Or possibly @TennesseeTony.I wasn't (intentionally) "bunkering", BTW. I just made possibly a poor choice at the start of the race, to arm my two 6C/12T Ryzen 3600 CPU rigs, with 12 tasks each, each 1 thread per task. So, then I had to wait like 5 days to finish those tasks. I've since switched to 3 tasks, 4 threads ea.
llrCUL still seems to be at 2M. llrWOO may be at 2340K now (this is 18 MByte size) and thus a bit much for Zen2. It's zero-padded data though; I don't know if the processor cache management handles this more efficiently than fully populated data.A quick and superficial look at the PG web site shows me that llrCUL is now using about 2 M long FFTs on FMA3 supporting hardware like Ryzen 3000. This means circa 16 MByte footprint of the hottest program data, per each task.
Ah, yes, I uhm, was fixated on hitting 20 years at WCG for Covid. I will jump on the bandwagon soon.I didn't mean you with the "no bunkering" hint. I mainly meant @StefanR5R. Or possibly @TennesseeTony.
I know I've noticed that, since I've been crunching with a small numeric WU limit, I'm getting a lot less of the short double-check WUs. It's probably something like that.How did 'Team Norway' slip in ahead of us, with like 100 less WUs crunched. Are they only crunching the "easy" WUs or something?
Famous last (place? ) words. I fired up a cloud system thinking it would help me with @emoga. I didn't even see @crashtech crashing through the ranks!Anyways, you're going to likely end up out front, Ken_g6
I didn't mean you with the "no bunkering" hint. I mainly meant @StefanR5R. Or possibly @TennesseeTony.
Couldn't help yourself, could you @StefanR5R? Well, at least you didn't crash their server...this time.Nevermind, @lane42 , xii5ku just blew by us, causing us to veer off course a bit from all the dust, smoke and Mach 3+ turbulent air.... Stefan needs to name one of his rigs 'SR-71', and another 'Blackbird'.
I have been told a long while ago that disk space for result files is allocated on the server when a task is generated or when a task is assigned to a host. (I don't recall which of these two.) Either Michael Gutierrez formulated his warning very wrong (the disk space is not occupied between uploading and file deletion; it is occupied from when a task is in progress, until file deletion), or they modified their server to overcommit its disk space.In the previous llrDIV challenge announcement Michael Gutierrez said:This subproject uses LLR2, which means dumping bunkers will be disastrous for the server. It will fill up the server's disk drive.
Either this statement is incorrect, or they implemented a faulty protection which would prevent forward progress of the server. I don't believe that the PG admins are this dumb, rather I believe that this warning was incorrect.Michael Gutierrez said:As a result, the server will stop accepting uploads. That will be bad for all users, of course, but it will be worse for the people who have been holding bunkers. You may miss out on uploading your entire bunker if we shut down uploads.
I merely had 24 results to upload and report today. Which, as to be expected, went through in the blink of an eye.
As a frame of reference, the top three teams combined reported 67 results per hour on average throughout the challenge.
I am sure that the PrimeGrid server can handle challenges at projects like llrCUL and llrWOO with ease. PPS(E), SGS and the likes would be a lot more demanding for the server.
Nevermind, @lane42 , xii5ku just blew by us
Tony, who is this guy xii of which you speak. Do you mean theRank___Credits____Username
74_____1600961____crashtech
101____1139530____emoga
106____1072414____Ken_g6
118____978838_____Orange Kid
136____752161_____VirtualLarry
156____611763_____Lane42
157____610049_____xii5ku