All of lore.kernel.org
 help / color / mirror / Atom feed
* DNS server reading directly from reiserfs
@ 2002-05-02 10:39 Phil Howard
  2002-05-02 10:37 ` Hans Reiser
  0 siblings, 1 reply; 2+ messages in thread
From: Phil Howard @ 2002-05-02 10:39 UTC (permalink / raw)
  To: reiserfs-list

Continuing from an earlier discussion I had regarding the use of reiserfs
based files in place of databases, I was thinking about the issues involved
in serving DNS data directly from files.  The concern I had previously was
the performance hit from open(),read(),close() to access a single piece of
data to answer a query.  Today I realized that DJBDNS uses the CDB format
and does an open(),read(),close() sequence for each query as well.  So it
can't be that bad.  This would come down to reiserfs vs CDB for which is the
faster in finding the desired piece of data, not the syscall interfaces, in
terms of comparing these two.  Assuming all data is in a single directory,
or maybe is in a directory tree structured TLD-first, what performance level
might one expect doing this?  With ext2 it could be quite costly due to the
O(N) lookup.  With reiserfs tree structure, this would be a lot better.  And
with tail-packing, less RAM would be needed to keep lots of data in cache
for large servers.  Any thoughts or benchmark data along these lines?

-- 
-----------------------------------------------------------------
| Phil Howard - KA9WGN |   Dallas   | http://linuxhomepage.com/ |
| phil-nospam@ipal.net | Texas, USA | http://phil.ipal.org/     |
-----------------------------------------------------------------

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2002-05-02 10:39 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-05-02 10:39 DNS server reading directly from reiserfs Phil Howard
2002-05-02 10:37 ` Hans Reiser

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.