David G. Kanter
25 June 2005, 01:45 AM
. . .Another reason this solution is less-than-ideal is that switching indexes (Soundex->Last name, and back) takes *far* too long. Some thought needs to be given in future version towards optimizing algorithms for large files - anything involving indexing, including match & merge, takes much longer than is necessary!I appreciate the computer's processor speed and RAM, along with the size of the Family File, would have a direct impact on the time for those operations, but I'll offer the following times for my Ti PowerBook—with a 1 GHz processor and 1 GB of RAM—on my Family File with 22,482 persons—under OS 10.4.1:
• A re-sort of the Index from any of the 10 options to another option takes less than 1 second.
• A Find Relatives takes about 7 seconds.
• A rebuild of the whole Index takes about 14 seconds. (This is an operation that happens very infrequently for me—usually only after I've chosen to save a Compact Copy and then open that copy.)
(I'm not addressing "match & merge" as if you're using it for a large number of persons against a large number of persons it is, understandably, a very intensive operation; but for me, that's an infrequently used feature—and then it's usually a "few against many" operation.)
I'm not in a position to know what trade-offs are appropriate within Reunion that might further accelerate the various operations for whatever is Dennis' computer, but for the overwhelming majority of the operations I use, Reunion is waiting for me, not the other way around—and that's on a computer which has become relatively slow compared to every Mac that is being sold now. (Who would have believed that, say, 5 years ago?)
• A re-sort of the Index from any of the 10 options to another option takes less than 1 second.
• A Find Relatives takes about 7 seconds.
• A rebuild of the whole Index takes about 14 seconds. (This is an operation that happens very infrequently for me—usually only after I've chosen to save a Compact Copy and then open that copy.)
(I'm not addressing "match & merge" as if you're using it for a large number of persons against a large number of persons it is, understandably, a very intensive operation; but for me, that's an infrequently used feature—and then it's usually a "few against many" operation.)
I'm not in a position to know what trade-offs are appropriate within Reunion that might further accelerate the various operations for whatever is Dennis' computer, but for the overwhelming majority of the operations I use, Reunion is waiting for me, not the other way around—and that's on a computer which has become relatively slow compared to every Mac that is being sold now. (Who would have believed that, say, 5 years ago?)