> you could study the hints and configurations that MUST be tweaked for YOUR hw, > sw, network, and app behaviour. > It was used for php sessions for a groupware: > http://www.techforce.com.br/news/linux_blog/glusterfs_tuning_small_files > The client side and server caches, the flush periods, and io-threads count are > *critically* dependent of hw, net, and app behaviour. I hear you, I had followed this article specifically in an attempt to improve performance. I suppose I'm hoping for more specifics on how these values correspond to an application, a number of cpu's, a brand of network card, etc. io-threads counts, for example, only seem to drive load average higher, as they all sit there chewing up cpu anyway, so you lower them and get lower overall system load but higher latency. But why would the glusterfs process need cpu time anyway? John -- John Madden Sr UNIX Systems Engineer Ivy Tech Community College of Indiana jmadden at ivytech.edu
