Subfield 5 is now on it's final batch (16x12).

This is the first batch of WUs generated since the app was optimized. As a result, run times will be going up. These WUs average 2 hour run times on my AMD Ryzen 2990WX. Note there are 1.6 million of them; with the unoptimized app it would have required 16 million, so this is a huge improvement.

I will be mixing in some subfield 6 WUs with this batch. These were generated a while ago for the unoptimized app, so will run very quickly by comparison. If I were to run them independently, it might put too much of a strain on the server, so I figured this is a good way to get them done (without having to re-generate them which can be tedious).

Very good new :-)

I know that i havent been much active here since i am working on my own stuff, but its good to hear that this project is moving forward!
Quick heads-up: SF6 will give us (at least) 58M tasks, so there will be work for quite a long time~
(an other heads up: total amount of all workunits from the Decic Search is now at 88,411,891; we are getting closer to 100M. No doubt we are going to get over 100M :D Fun fact, said number is prim. ^^)

But I´d like to ask when we will get the remaining Batches from SF3, like 13x270.
That could be loaded together with SF6 after SF5 is fully done, or?

I know that i havent been much active here since i am working on my own stuff, but its good to hear that this project is moving forward!
Quick heads-up: SF6 will give us (at least) 58M tasks, so there will be work for quite a long time~
(an other heads up: total amount of all workunits from the Decic Search is now at 88,411,891; we are getting closer to 100M. No doubt we are going to get over 100M :D Fun fact, said number is prim. ^^)

But I´d like to ask when we will get the remaining Batches from SF3, like 13x270.
That could be loaded together with SF6 after SF5 is fully done, or?

Actually, I thought we would tackle the rest of SF4 first. It should be quicker than SF3.

This is the first batch of WUs generated since the app was optimized. As a result, run times will be going up.

Has the "Estimated computation size" been increased accordingly? Mine still say 1,000 GFLOPS, which is what I remember as it always saying. So I think that I'm downloading more than I should be, given that they now take longer.

Has the "Estimated computation size" been increased accordingly? Mine still say 1,000 GFLOPS, which is what I remember as it always saying. So I think that I'm downloading more than I should be, given that they now take longer.

I believe it only uses that value initially. For a given host, after enough WUs have been processed, it starts using a moving average. Because the runtime went up, the average will lag behind, and in the short term you will download more WUs. Shouldn't take too long to correct.

If you have more WUs than you can finish, you can always abort some of them.

16×12 as 86.5% complete with 6.1 days remaining as of 13 Jun 2019, 1:00:01 UTC