View Single Post
Old 2018-04-16, 19:14   #1
EdH's Avatar
"Ed Hall"
Dec 2009
Adirondack Mtns

10010010100112 Posts
Default Duplication of Effort for Smaller Aliquot Sequences

This has been brought up previous, but I thought I'd address it again, since I was reviewing the "Blue Page" recently and it came back to mind.

Since I probably qualify as an elf in my composite work with the db, I'm concerned about duplication of effort with such entities as yafu@home. I'm not familiar with the project enough to be sure, but if the system in use updates the db with each new line for a sequence, that new line holds a composite with <=100 digits, and the system continues with the new composite itself, there may be duplication.

Right now there are very few composites <100 dd in the db. When one shows up, it is quite often taken for factorization within a few seconds. If that same composite has already been in work by yafu@home, or another entity using a procedure that sends each new line to the db, there is duplication. (See, Is there a tool that picks off small composites constantly?.)

For the above reasons, I would like to suggest (again) that if an entity is working a sequence that reaches the db's major composite backlog, (currently the low end is 100 dd), that it either be left for the db to work**, either to termination or return above the backlog, or the sequence could be worked locally instead of updating the db at that time.

I'm not trying to pick on anyone, e.g. yafu@home, but I have seen many of my C100s turned away by the db due to already being factored by the time my machine finished. For my antique machines, a C100 can represent anywhere from twenty minutes to an hour and a half.

**If the db does terminate a sequence the credit should still be claimed by the reservation holder.

Further comments, critiques, etc. accepted...
EdH is offline   Reply With Quote