[1283] in Kerberos_V5_Development
Re: changing libkdb database open/lock semantics
daemon@ATHENA.MIT.EDU (Christopher Provenzano)
Tue Jun 4 18:45:53 1996
Reply-To: proven@cygnus.com
To: "Barry Jaspan" <bjaspan@MIT.EDU>
Cc: krbdev@MIT.EDU
In-Reply-To: Your message of "Tue, 04 Jun 1996 13:05:48 EDT."
<9606041705.AA25476@DUN-DUN-NOODLES.MIT.EDU>
Date: Tue, 04 Jun 1996 17:35:24 -0400
From: Christopher Provenzano <proven@proven.org>
>
> Yes, I am looking into this bug now and would prefer to find it than
> change the implementation to something that is MUCH slower.
>
> If you can fix the bug using the current semantics, that's fine with
> me; I only want something that works. Assertions about "much slower"
> shouldn't be made without evidence, however. MIT has Quantify for
> SunOS and Solaris, so evidence should be easy to obtain; I'm happy to
> generate results for my modified libkdb.
I did some benchmarks last year when I changed the code to it's current
implementation. The time to get and decode a db entry was increased by
a factor of 10.
CAP
