Re: Problem with program (Pirko's RPSORT)
- From: "SevagK" <spamtrap@xxxxxxxxxx>
- Date: Fri, 26 Aug 2005 06:42:50 +0000 (UTC)
=Robert===================================
... must be able to eliminate dulicate records,
...
==========================================
This implies that a record ID has to be kept in memory somewhere to check
for duplicates, this ID could be a variable length string perhaps. With
400_000 records, you'll probably run out of memory pretty fast.
This could also be the source of the speed problem. As records grow, the
look-up hash table (if that is used) would grow as well (probably
resulting in large chunks of mem->mem copies), plus there are concerns of
swapdisk memory usage.
-kain
.
- Follow-Ups:
- Re: Problem with program (Pirko's RPSORT)
- From: Robert Redelmeier
- Re: Problem with program (Pirko's RPSORT)
- References:
- Problem with program (Pirko's RPSORT)
- From: prino
- Problem with program (Pirko's RPSORT)
- Prev by Date: Re: HLA macro question?
- Next by Date: Re: HLA macro question?
- Previous by thread: Re: Problem with program (Pirko's RPSORT)
- Next by thread: Re: Problem with program (Pirko's RPSORT)
- Index(es):
Relevant Pages
|
|