Kashani wrote:
ReiserFS does deal with billions of tiny files better than almost all other file systems. You're going to run into inode issues with ext3 as well. However what you're doing sounds like it belongs in a database instead of creating weird data structures within your filesystem.
Kashani,
Thanks, I searched and found some docs that indicate this too. Your answer was much better than Dave Nebinger's of "search for 'unmaintainable ridiculous software architecture'", that wasn't helpful at all.
David,
To be honest I had an edit that looked suspiciously like Dave's. I edited because very few people have had a million files/dirs in a file system much less a billion, so I assumed a certain naivety on your part.
The idea of using your file system as data structure is tempting because in the beginning it does work and it's simple. After a certain size you start running into really strange problems, backing up becomes next to impossible, you start getting really weird performance, and you use much more space than your 32kb files would lead you to believe.
Your design is unworkable. And if you think scanning a db is going to be slow wait till you implement this.
kashani
-- [email protected] mailing list
