Forgot about tmpfs...maybe not for this project but it will be useful in others...thanks
FYI, if anyone is interested, the way I setup mine I have two scripts 1. mount-temp (which mounts the tmpfs, then untars a saved directory) 2. unmount-temp (which first make a tarball of the directory, then unmounts) First I created the tmpfs, then created UV account in tempfs linked an accountname to that directory. The cool part here, is you can create a skeleton UV account then save that. Modify your programs to do what you want, and tar that account restore the skeleton, and repeat for different tasks. This way your tmpfs can be used for different tasks, each with their own files and programs (their own tarball). George > -----Original Message----- > From: [email protected] [mailto:u2-users- > [email protected]] On Behalf Of Glen Batchelor > Sent: Friday, August 28, 2009 1:39 PM > To: 'U2 Users List' > Subject: Re: [U2] back to the socket problem.... > > > The main benefit of using sockets is to have a single point of access > from > the client side and the ability to implement ACLs by IP and port. If > you can > queue your requests via file and perform multiplexed reads/writes using > a > pool of phantoms, then you can actually handle higher throughput for > requests. You also don't have the network resources to contend with. If > you > are using *nix consider creating a tmpfs mount and do your transactions > there instead of a disk location. You'll be surprised at how fast you > can do > I/O with a tmpfs compared to socket services. If you have to have > sockets, > consider dumping the requests and reading the responses using > inetd/xinetd > and a standard I/O script. This is similar to how MVWWW does HTTP > request/response spooling. > > http://mvwww.sourceforge.net > > ---------------------------------------- > Glen Batchelor _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
