Quote:
Originally Posted by warachwe
This is what I guess was happened.
On 15 ^{th} November, someone enter a number of form b ^{n} with b<20000 and n<1000 or somewhere around that ballpark. Since then DB slowly determined whether each number is prime, and while doing so produced a factor which is product of small prime. When that factor is more than 19 digit it won't get factor more. (I think the DB automatically does this for all unknown number less than 20,000 digits). This is where those small composite came from.
The problem is there might be up to 10^7 unknown number waiting in queue, according to Distribution of numbers by digits. Those will continue to produce small composite for quite a while.

2.2M <70 when I checked a few minutes ago. Why would the db not pull out p1p10 primes first if it was breaking down larger composites? Almost all of these are made up of <10 digit primes.
Quote:
Originally Posted by penlu
I can't get enough numbers to run into the page request limit. Instead I've been running into the "IDs created" limit. Submitting a factorization of a number into a product of many small (< 10000) primes seems to create many IDs; I don't understand why.

Any time a "never before seen" number arrives, it is added to the db and generates a new ID. It does seem odd that many of these small composites are composed of primes not already known. I would think this would eventually not be the case, unless the db handles small primes in a different manner from others. But, the IDs for primes <19 are the prime itself. Perhaps these primes are not kept which forces a new generation flag every time it shows up.
On a somewhat related issue, can anyone untar the .bz2 files generated on the Downloads page? I tried
List of 1.000 randomly chosen, small composite numbers and I can't open the file with anything. I just get errors.
Similarly, can several factorizations be uploaded at once instead of individually?