Factordb wipeout? - Page 4

richs · 2019-12-10, 01:44

Moved my one core of an i3 to 83 digits since the 81's are cleared out.

EdH · 2019-12-10, 04:03

Quote:

Originally Posted by richs

Moved my one core of an i3 to 83 digits since the 81's are cleared out.

I've got everything here that's running composites aimed at 82 for now. I'll try to keep better attention as 82 dwindles. . .

EdH · 2019-12-10, 14:17

Quote:

Originally Posted by richs

Moved my one core of an i3 to 83 digits since the 81's are cleared out.

This morning I started some sessions at 79, since you're now at 83 and 79-81 are trying to build back up. . .

Stargate38 · 2019-12-12, 20:27

It seems the DB is down for maintenance atm. I'm guessing that Syd's adding more disk space (i.e. adding HDDs), or possibly fixing the broken Aliquot sequences.

EdH · 2019-12-14, 16:11

Quote:

Originally Posted by richs

Moved my one core of an i3 to 83 digits since the 81's are cleared out.

Well, I'm impressed! I set loose 8 i7s (all 8 cores), plus 2 RPis (all 4 cores - ECM only) on 84 digits overnight and you kept 83 digit factoring just about even with my 84 digit work.

I noticed a little less than 200 in the 79-82 area this morning, so I set all four cores of an i5 and a Colab session to work there and now there are over 200!

richs · 2019-12-15, 01:02

Quote:

Originally Posted by EdH

Well, I'm impressed! I set loose 8 i7s (all 8 cores), plus 2 RPis (all 4 cores - ECM only) on 84 digits overnight and you kept 83 digit factoring just about even with my 84 digit work.

I noticed a little less than 200 in the 79-82 area this morning, so I set all four cores of an i5 and a Colab session to work there and now there are over 200!

Well someone else must be doing the heavy lifting on 83 digits since I'm only averaging 15 composites per hour.

chris2be8 · 2019-12-15, 16:58

I'm working on 83 digits in the gaps between clearing 70-79 digits. But that's taking most of my time now so I'm only doing about 20/hour. Mostly after skipping 40000-5000 composites to keep clear of your work.

And just look how many have built up under 70 digits. Factordb will take a while to clear that lot.

Chris

2019-12-12, 20:27	#37
Stargate38 "Daniel Jackson" May 2011 14285714285714285714 3×13×17 Posts	It seems the DB is down for maintenance atm. I'm guessing that Syd's adding more disk space (i.e. adding HDDs), or possibly fixing the broken Aliquot sequences. Last fiddled with by Stargate38 on 2019-12-12 at 20:29

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
A suggestion for factordb.	enzocreti	FactorDB	15	2021-06-24 07:15
Spammers in FactorDB	wpolly	FactorDB	5	2019-04-16 11:19
Extending Factordb	carpetpool	FactorDB	6	2017-01-23 11:04
FactorDB PRP's	smh	FactorDB	231	2015-07-28 02:30
FactorDB question	Raman	Factoring	15	2010-01-28 10:24

2019-12-10, 01:44	#34
richs "Rich" Aug 2002 Benicia, California 1306₁₀ Posts	Moved my one core of an i3 to 83 digits since the 81's are cleared out.

2019-12-15, 16:58	#40
chris2be8 Sep 2009 100000011110₂ Posts	I'm working on 83 digits in the gaps between clearing 70-79 digits. But that's taking most of my time now so I'm only doing about 20/hour. Mostly after skipping 40000-5000 composites to keep clear of your work. And just look how many have built up under 70 digits. Factordb will take a while to clear that lot. Chris