On Tue, 27 Sep 2005, tedemo wrote: > >When the hash size is about 20 million entries, that alone requires ~80MB > >physical memory. If resizing is triggered, at least two times of that > >amount of memory is needed temporarily. > > > The problem was comming from the --probes parameter which was set to 2 ! > Increasing its value to 10, reduced the hashsize up to a factor 100. Thus you trade memory for speed: lookups in the set will be ten times slower. Still I don't get how does it come that the initial hash size was so huge. Best regards, Jozsef - E-mail : kadlec@xxxxxxxxxxxxxxxxx, kadlec@xxxxxxxxxxxxxxx PGP key : http://www.kfki.hu/~kadlec/pgp_public_key.txt Address : KFKI Research Institute for Particle and Nuclear Physics H-1525 Budapest 114, POB. 49, Hungary
