On 01/11/2007, Harris Landgarten <harrisl@xxxxxxxxxxxxx> wrote: > BTW, > > Is there any doc on booster? Here is some info about booster: -------- The booster translator gives applications a faster path to communicate read and write requests to GlusterFS. Normally, all requests to GlusterFS from applications go through FUSE. Using the booster translator in conjunction with the GlusterFS booster shared library, an application can bypass the FUSE path and send read/write requests directly to the GlusterFS client process. The booster mechanism consists of two parts: the booster translator, and the booster shared library. The booster translator is meant to be loaded on the client side, usually at the root of the translator tree. The booster shared library should be LD_PRELOAD'ed with the application. The booster translator when loaded opens a Unix domain socket and listens for read/write requests on it. The booster shared library intercepts read and write system calls and sends the requests to the GlusterFS process directly using the Unix domain socket, bypassing FUSE. This leads to superior performance. Once you've loaded the booster translator in your volume specification file, you can start your application as: $ LD_PRELOAD=/usr/local/bin/glusterfs-booster.so your_app The booster translator accepts no options (yet). ------- Vikas -- http://vikas.80x25.org/
