This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/

slow indexdb

Previous message (by thread): slow indexdb

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Daniel Karrenberg Daniel.Karrenberg at ripe.net
Thu Jun 26 10:44:28 CEST 1997

Gabor,

sorry I could not respond earlier. I was out of the office in the
beginning of the week. David has already given an extensive answer
showing that there is not one simple answer to this. In general
it helps to have more memory. Specifically you can look at your dbm
implementation and the need for inverse indices as David has 
indicated. 

If you have any further questions, please do not hesitate to contact us.

Kind regards

Daniel Karrenberg
RIPE NCC Manager

  > Gabor Kiss <kissg at zeronull.aszi.sztaki.hu> writes:
  > 'indexdb -s RIPE' runs 8 hours on a 4 processor SparCenter 2000.
  > Is this normal? What are your experiences?
  > 
  > Gabor
  >

Previous message (by thread): slow indexdb

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]