At 09:20 PM 11/09/00 +0000, Tim Bunce wrote:
>On Thu, Nov 09, 2000 at 08:27:29PM +0000, Matt Sergeant wrote:
>> On Thu, 9 Nov 2000, Ask Bjoern Hansen wrote:
>> > If you're always looking stuff up on simple ID numbers and
>> > "stuff" is a very simple data structure, then I doubt any DBMS can
>> > beat
>> >
>> > open D, "/data/1/12/123456" or ...
>> >
>> > from a fast local filesystem.
>>
>> Note that Theo Schlossnagel was saying over lunch at ApacheCon that if
>> your filename has more than 8 characters on Linux (ext2fs) it skips from a
>> hashed algorithm to a linear algorithm (or something to that affect). So
>> go careful there. I don't have more details or a URL for any information
>> on this though.
>
>Similarly on Solaris (and perhaps most SysV derivatives) path component
>names longer than 16 chars (configurable) don't go into the inode
>lookup cache and so require a filesystem directory lookup.
Ok, possibly 8 chars in Linux and 16 under Solaris. Anything else to
consider regrading the maximum number of files in a given directory?
How about issues regarding file size? If you had larger files/records
would DBM or RDBMS provider larger cache sizes?
Bill Moseley
mailto:[EMAIL PROTECTED]
