I would suspect aggressive caching of some data describing every file touched by the glusterfs client. In fact, these data seem to be kept forever, as the memory is never freed and no new allocations are made, if the same files are accessed for the second time. It is sufficient to run ls -R or du on a big directory tree and run top, to see the memory usage of glusterfs client increasing nicely up to hundreds of megabytes. John, do you see it too?
No, the glusterfs client procs sat at pretty low memory use regardless of cache settings (actually made me wonder if those settings were even working).
John -- John Madden Sr UNIX Systems Engineer Ivy Tech Community College of Indiana [email protected] _______________________________________________ Gluster-users mailing list [email protected] http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
