BDB performance when keys are long

X-Received	by 10.224.51.68 with SMTP id c4mr5761389qag.7.1379519122076; Wed, 18 Sep 2013 08:45:22 -0700 (PDT)
X-Received	by 10.50.8.42 with SMTP id o10mr1052699iga.3.1379519121998; Wed, 18 Sep 2013 08:45:21 -0700 (PDT)
Path	csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!d5no383547qap.0!news-out.google.com!gv3ni456qab.0!nntp.google.com!d5no423039qap.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups	comp.databases.berkeley-db
Date	Wed, 18 Sep 2013 08:45:21 -0700 (PDT)
Complaints-To	groups-abuse@google.com
Injection-Info	glegroupsg2000goo.googlegroups.com; posting-host=116.197.178.83; posting-account=dBBOEAoAAACLCZEAhLTluN88d8WTcAdS
NNTP-Posting-Host	116.197.178.83
User-Agent	G2/1.0
MIME-Version	1.0
Message-ID	<2e7d366c-06c2-45b6-9bb2-93d21bb5abf6@googlegroups.com> (permalink)
Subject	BDB performance when keys are long
From	Nilesh Simaria <nileshsimaria@gmail.com>
Injection-Date	Wed, 18 Sep 2013 15:45:22 +0000
Content-Type	text/plain; charset=ISO-8859-1
Xref	csiph.com comp.databases.berkeley-db:20

Show key headers only | View raw

In my app, I have keys in string format with length in range of 16 - 1024 characters. Max keys would be 1M.

How would be the key lookup performance of BDB in such case ? 

For such keys what would be the best access method ?

Thanks,
Nilesh

Back to comp.databases.berkeley-db | Previous | Next | Find similar

Thread

BDB performance when keys are long Nilesh Simaria <nileshsimaria@gmail.com> - 2013-09-18 08:45 -0700

csiph-web