Certificate : For all indents and purposes

[EdH]

Originally Posted by pakaran

Is there anything I can help with?

BTW, good to see you back. I may not have seemed cheerful enough in my previous message. Will you be back for a while?

Here are the ids for the troublesome candidates:

1100000001046468738 size 2412
1100000000781996714 size 2531
1100000000953365184 size 2544
1100000001068764753 size 3927

As can be seen, the first three are 2xxx and the last one is 3xxx. Hopefully these can someday be removed in some manner.

[pakaran]

If those become overly annoying to watch fail, I could delete them by script. I'm planning to be active for awhile, yes, and I could have been more courteous myself. There's no particular concrete need for me to work on the smallest numbers; I could take a small subrange between 4000 and 4100 dd, if nothing else.

As it stands, I'm happy to work below 3k for awhile, and will speak up if I get overwhelmed.

[EdH]

Originally Posted by pakaran

If those become overly annoying to watch fail, I could delete them by script. I'm planning to be active for awhile, yes, and I could have been more courteous myself. There's no particular concrete need for me to work on the smallest numbers; I could take a small subrange between 4000 and 4100 dd, if nothing else.

As it stands, I'm happy to work below 3k for awhile, and will speak up if I get overwhelmed.

Let me know what you'd like. I've been trying to move the lower edge to 4000 dd and it is there now, except for the new arrivals. Those new arrivals do seem to be coming a bit faster these days. I'm running 4 in the 3xxx range and several others in the 400x range.

However, my db use has somehow just been severely limited, in which case, I may stop entirely:

Resources used by your IP (?)
Page requests 14
IDs created 6
Database queries 252
CPU (Wall clock time) 1,507.3 seconds
You have reached your hourly limit of 750 seconds CPU-time.
Counting since January 29, 2018, 4:45 pm 

[chris2be8]

I've had a similar outage (or rather my script adding algebraic factors did). It started saying

You have reached the maximum of 4 parallel processing requests ?. Please wait a few seconds and try again.

Then changed to

You have reached your hourly limit of 750 seconds CPU-time.

a few minutes later.

It cleared after about 30 minutes.

So it was probably a glitch in factordb since it hit us both at about the same time.

Chris

[EdH]

Originally Posted by chris2be8

I've had a similar outage (or rather my script adding algebraic factors did). It started saying

You have reached the maximum of 4 parallel processing requests ?. Please wait a few seconds and try again.

Then changed to

You have reached your hourly limit of 750 seconds CPU-time.

a few minutes later.

It cleared after about 30 minutes.

So it was probably a glitch in factordb since it hit us both at about the same time.

Chris

Thanks! Mine cleared exactly at an hour (5:45 db time) and I had the parallel requests page, too, but I figured that was due to all my composite machines trying to get more composites all at once.

I ended up leaving my Primo machines running, but stopped everything else. Maybe I'll bring the others back up and see what happens...

[EdH]

Hey Pakaran,

Are you still working from the 300 range up or are you grabbing anything in the 2xxx area? I see we're really gaining a bunch of candidates below 3xxx and wondered if I should move my lower bound back down some. I'll wait a couple days to hear from you before I make any downward move, but we seem to be gaining entries at a pretty healthy rate.

[MisterBitcoin]

Just noticed +10K PRP´s today, most of them where <300 digits.

[pakaran]

I am still working, will start a new "sweep" now.

[pakaran]

Over the weekend I uploaded certs for most numbers below ~1k dd (working in order of input file size). I'll keep going.

[pakaran]

This week, on two occasions, I've seen numbers already proven when I uploaded them. Once, I had been running only a few hours before submitting them. If anyone else is working in the smaller numbers, I'd appreciate knowing to avoid duplication of effort. In the mean time, I'm going back to non-Primo tasks.

[EdH]

Originally Posted by pakaran

This week, on two occasions, I've seen numbers already proven when I uploaded them. Once, I had been running only a few hours before submitting them. If anyone else is working in the smaller numbers, I'd appreciate knowing to avoid duplication of effort. In the mean time, I'm going back to non-Primo tasks.

I've been quite busily running all the new 3xxx to catch back up with my 4xxx area and haven't ventured downward at all. But not all the contributors are watching this thread.

I haven't any suggestions on how to proceed, unless you want to work the higher end of the range. The factordb default is 300 dd, so any new contributors would probably start there.