strange thing happening in factordb

[yoyo]

Think it can't be changed to use primo. As I know primo isn't available as command line tool.
yoyo

[pinhodecarlos]

Originally Posted by yoyo

Think it can't be changed to use primo. As I know primo isn't available as command line tool.
yoyo

Maybe we could write to primo author explaining our objective and telling about factordb.com...

[schickel]

Originally Posted by pinhodecarlos

Maybe we could write to primo author explaining our objective and telling about factordb.com...

I don't know about that. He has discontinued development on the Windows version, and pulled the Large Integer package he had available for Delphi/C++ Builder. He seems very down on MS for some reason (could be based on the headline on his front page....)

He is still working on the Linux version, however, and it will be able to blow the Windows version out of the water, since it has multi-core capability built in...

[EdH]

Although Ellipsa (the 64-bit linux version of primo), isn't command line friendly, I have done a lot of the 1000-1355 digit certificates with it on a couple of my machines over the last few weeks. The fact that you can load a batch of certificates at once allows for less manual work. Granted, it's not doing everything itself, but all I do is d/l a batch of *.in files from the db, unzip, start Ellipsa, build, load and come back later to zip and report. If I want to let it run through tomorrow, I d/l more *.in files. If I want to check it in a few hours, I do a single size digit group. Right now I have one machine doing 1354 digits and the other doing 1355 digits. I'll u/l them in a few hours. Then I'll probably set one machine to work overnight.

[henryzz]

Originally Posted by EdH

Although Ellipsa (the 64-bit linux version of primo), isn't command line friendly, I have done a lot of the 1000-1355 digit certificates with it on a couple of my machines over the last few weeks. The fact that you can load a batch of certificates at once allows for less manual work. Granted, it's not doing everything itself, but all I do is d/l a batch of *.in files from the db, unzip, start Ellipsa, build, load and come back later to zip and report. If I want to let it run through tomorrow, I d/l more *.in files. If I want to check it in a few hours, I do a single size digit group. Right now I have one machine doing 1354 digits and the other doing 1355 digits. I'll u/l them in a few hours. Then I'll probably set one machine to work overnight.

I just did a similar technique to kill the tail upto 1300 digits. Easy to do. Might be an idea to create a thread containing info on who is doing what so there is no overlapping. EdH is doing certificates at ~1350 and I am keeping the tail behind him gone currently. There also isn't a central place where we can clearly see who is factoring composites at what digit levels currently.

[schickel]

Originally Posted by EdH

Although Ellipsa (the 64-bit linux version of primo), isn't command line friendly, I have done a lot of the 1000-1355 digit certificates with it on a couple of my machines over the last few weeks. The fact that you can load a batch of certificates at once allows for less manual work. Granted, it's not doing everything itself, but all I do is d/l a batch of *.in files from the db, unzip, start Ellipsa, build, load and come back later to zip and report. If I want to let it run through tomorrow, I d/l more *.in files. If I want to check it in a few hours, I do a single size digit group. Right now I have one machine doing 1354 digits and the other doing 1355 digits. I'll u/l them in a few hours. Then I'll probably set one machine to work overnight.

The same thing works for the GUI version, except that you would run up against its ceiling sooner or later.

Too bad there's not a way to look up certs by user; I did some the last time we went through this, but I don't remember how high I went.

[EdH]

Originally Posted by henryzz

I just did a similar technique to kill the tail upto 1300 digits. Easy to do. Might be an idea to create a thread containing info on who is doing what so there is no overlapping. EdH is doing certificates at ~1350 and I am keeping the tail behind him gone currently. There also isn't a central place where we can clearly see who is factoring composites at what digit levels currently.

We could always set up a thread, if needed for digit reservations. No one has been duplicating more than a couple here and there for all the ones I've done in the last few weeks, though. If more get involved, we may need to start that thread and reservations.

Or, a second more reaching thought, that would have to be left to Syd, would be a way to lock composites and primo batches for a short time, so as not to duplicate what is handed out. Since each number is tagged with an ID, it might be possible to issue a number or batch, lock it against reissue for a short time, allowing for processing and then either complete it, if results are received or free it up for someone else to work, if results are not received within the lock time. I'm not sure how difficult something like that would be to implement, or if this is even of interest at this time.

I have several machines that default to yoyo's script, so they're working composites, until I assign them something else. Unfortunately, I'm also running into this too often:

unable to allocate 1003439448 bytes for range 0 to 0
Error, no result found

In this case, no result would be returned, but the lock would have to run out before the composite could be reassigned.

[RichD]

Originally Posted by schickel

Too bad there's not a way to look up certs by user

Not by user but a list like this is available.

Start on the Status page and click on the number of certs, then go from there.

[schickel]

Originally Posted by RichD

Not by user but a list like this is available.

Start on the Status page and click on the number of certs, then go from there.

Yeah, I knew about the list, but sitting and trolling through a bunch of pages to find your name is pretty boring. Unless you can find yourself at a landmark....so I guess that answers how high the latest Primo can go: at least 2976 digits.

[EdH]

Originally Posted by schickel

....so I guess that answers how high the latest Primo can go: at least 2976 digits.

According to the Primo Top-20 page, the highest so far is 12903 decimal digits. (sounds like a nearby zip code...)

edit: I'm actually thinking of trying something large, but not quite that big. 7 months is a bit of a stretch for my attention span...

[schickel]

Originally Posted by EdH

According to the Primo Top-20 page, the highest so far is 12903 decimal digits. (sounds like a nearby zip code...)

edit: I'm actually thinking of trying something large, but not quite that big. 7 months is a bit of a stretch for my attention span...

And that was with splitting the task among other computers and recombining the pieces by hand. So I guess my comment should be more along the lines of "3000 digits without special effort and in a resonable time".

I can provide some timings if you like (after my current NFS job finishes).