[reiserfs-list] DNS server reading directly from reiserfs
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/ | | [EMAIL PROTECTED] | Texas, USA | http://phil.ipal.org/ | -
Re: [reiserfs-list] DNS server reading directly from reiserfs
Phil Howard wrote: >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? > > > You never know until you measure. Try it! Hans