>Narendra Kumar S.S wrote: >> I think we need to brainstorm on this. >> What are the other ways that we can handle this? >> What are the implications , if we put a size limit on the contents file >> and when it reaches the max_size, open a second file. >> How does other OSes handle this? > >I think you need to go a little lower first. A size limit isn't useful >if the contents need to be sorted. So, an easy first question is, does >the file need to be sorted? If not, then does the file need to be ASCII >or would a DB file be better?
Been there, done that, turned out to be a disaster; was shipped and then removed. This may have been an implementation issue, because a generic DB was used which ran 512MB systems out of memory making upgrades *really* slow. (Thrashing memory with a large process is much more expensive than just writing a large file over and over again) I've done a prototype which was much faster but somehow the people in charge are determined to pile a ton of mechanisms on top of this such as "doors as files". Too many mechanism, a daemon running to create the file on the fly, etc. I think it can be solved with a low-tech solution which retains the contents file. Casper
