Although the list does not look impressive, much was accomplished in 2017. The sub-searches that were completed were some of the longest so far. In summary:
1. The search over Q(sqrt(2)) (subfield 3 of 7) completed several more tiers of the search. There are about 9 tiers left to go.
2. The search over Q(sqrt(-2)) (subfield 4 of 7) filled in a bunch more rows. This one has 7 tiers left to go.

Here are the goals for the new year:
1. Develop a GPU app. I have enlisted the help of a fellow user for this. This is a lofty goal and it could be many months before the GPU app is available. This app will be critical in completing the search over Q(sqrt(2)).
2. Complete the search over Q(sqrt(-2)).
3. Start the search over Q(sqrt(-5)) (subfield 5 of 7).

If you don't mind my asking about the GPU version, what would be it's minimum requirements to crunch? Would it be double-precision or single-precision heavy? And how heavy is it expected to be on the VRAM?

That's tough to answer at this point, at least for me since I've never written GPU code. I would guess double precision heavy, but since we are dealing with very large integers we will also need an arbitrary precision library. Not sure about the VRAM.

The person helping me is experienced with GPUs and probably has better answers. They may want to remain anonymous, so they may not respond directly to this post, but I will eventually get some more information for you.

I noticed that DS14x270 jumps.

Recently there were 20000 completed WUs. But now is 9000.

Is it OK?

Regards.

First of all thanks to Eric for protecting my privacy, but I have no problem answering directly ;-)

As Eric said, we are in a very early stage, so it is very difficult to give detailed requirements. Basically with GPU applications the guiding principle applies: more (of everything) is better / faster. Maybe we will give the user the possibility to fine-tune the app for their own hardware (via an appconfig.xml).

Since I personally prefer a test-driven development and only have a NVIDIA GTX 1080 Ti, one can assume that the GPU App is optimized for Nvidia cards first. Unless someone wants to sponsor a comparable and up-to-date ATI card.

As we develop the GPU App with OpenCL, i expect to see separate optimized applications for Nvidia and ATI GPUs as well as AMD / Intel CPUs with integrated graphics chips in the (far) future.

Of course, Eric and I like to keep you up to date with any news. But keep in mind that it will take some month, cause i can only work on it in my (limited) freetime.

I noticed that DS14x270 jumps.

Recently there were 20000 completed WUs. But now is 9000.

Is it OK?

Regards.

I think you are referring to the batch status page. The scripts that generate that are sometimes out of sync with the scripts that generate the work. To reduce server load I changed it so that the batch status is updated every 3 hours. It used to be every 15 minutes. The jumps you are seeing were always there, you just didn't notice it because it would correct itself within a few minutes.

When I find some time I will look into making my scripts a little more robust.

Will versions of the GPU app be available for both Windows and Linux?

---

That is the plan. After we have it working for one platform it shouldn't be too hard to port it to other platforms. However, I am not a GPU expert and am assuming the porting is as easy as porting normal C/C++ code.

Although the list does not look impressive, much was accomplished in 2017. The sub-searches that were completed were some of the longest so far. In summary:
1. The search over Q(sqrt(2)) (subfield 3 of 7) completed several more tiers of the search. There are about 9 tiers left to go.
2. The search over Q(sqrt(-2)) (subfield 4 of 7) filled in a bunch more rows. This one has 7 tiers left to go.

Here are the goals for the new year:
1. Develop a GPU app. I have enlisted the help of a fellow user for this. This is a lofty goal and it could be many months before the GPU app is available. This app will be critical in completing the search over Q(sqrt(2)).
2. Complete the search over Q(sqrt(-2)).
3. Start the search over Q(sqrt(-5)) (subfield 5 of 7).

Wow, 4760579 tasks )
It looks like we won't finish it this year.

Wow, 4760579 tasks )
It looks like we won't finish it this year.

I think we can do it...

25% of DS13x271 is completed )