From owner-freebsd-database Wed Jun 24 11:52:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA04352 for freebsd-database-outgoing; Wed, 24 Jun 1998 11:52:46 -0700 (PDT) (envelope-from owner-freebsd-database@FreeBSD.ORG) Received: from elektra.ultra.net (elektra.ultra.net [199.232.56.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA04204 for ; Wed, 24 Jun 1998 11:51:50 -0700 (PDT) (envelope-from syang@DIRHIT.COM) Received: from moe.dirhit.com ([10.4.18.2]) by elektra.ultra.net (8.8.8/ult.n14767) with ESMTP id OAA17888 for ; Wed, 24 Jun 1998 14:51:31 -0400 (EDT) Received: by MOE with Internet Mail Service (5.0.1459.74) id ; Wed, 24 Jun 1998 14:50:16 -0400 Message-ID: <839A86AB6CE4D111A52200104B938D435B4E@MOE> From: Steven Yang To: "'freebsd-database@FreeBSD.org'" Subject: OK, I think I fixed my own gdbm problem! Date: Wed, 24 Jun 1998 14:50:14 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1459.74) Content-Type: text/plain Sender: owner-freebsd-database@FreeBSD.ORG Precedence: bulk Hi, I think the culprit of my malloc error was the regularity of my test keys. I think the default gdbm hash function generated lots of hash collisions with my test queries, which I guess sucked up lots of RAM. I created random keys based on floating point values, and now I can generate larger files. Well, if you have any words of wisdom, I still welcome any help you can offer for things like optimizing for READ-ONLY databases! Steven Yang To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-database" in the body of the message