Hi Martin, On Tue, Aug 19, 2008 at 1:16 AM, Martin Fick <mogulguy@xxxxxxxxx> wrote: > --- On Thu, 5/15/08, Amar S. Tumballi <amar@xxxxxxxxxxxxx> wrote: > > > ''io-threads'' translator creates seperate > > threads (as specified by the option). But, it doesn't > > make sense to have more threads than number of CPUs > > available. It works good if the thread > > count is same as number of CPUs you have in server. > > Could you please explain the reasoning behind this statement? > Wouldn't adding multiple threads on a single CPU server still > allow a server thread to potentially serve files to other > clients while it is blocked serving one client? Couple of points to be noted are, * Apart from the io-threads, there is a separate fuse thread which reads/writes to /dev/fuse. * Since glusterfs operates in asynchronous framework, potentially there are very less scenarios, where a thread can block. Hence the purpose of io-threads is only for simultaneous executions. And the number of simultaneous execution paths is determined by the number of processors present. Can anyone confirm this? > > -Martin > > > > > > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxx > http://lists.nongnu.org/mailman/listinfo/gluster-devel > -- Raghavendra G A centipede was happy quite, until a toad in fun, Said, "Prey, which leg comes after which?", This raised his doubts to such a pitch, He fell flat into the ditch, Not knowing how to run. -Anonymous
