[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fuse-devel
Subject:    Re: [fuse-devel] fuse stat performance on multicore systems
From:       Han-Wen Nienhuys <hanwenn () gmail ! com>
Date:       2012-06-13 15:21:09
Message-ID: CAOw_e7YpdM0XO3KKvCbm_WTnJ_NGysw3xOkbPpCLTqKZdjLsow () mail ! gmail ! com
[Download RAW message or body]

On Wed, Jun 13, 2012 at 11:52 AM, Stefan Westerfeld <stefan@space.twc.de> wrote:

> So it seems that FuSE becomes really slow for stat/readdir when more than
> one CPU is available (probably because the userspace client and filesystem
> work ends up being done on different CPUs).

You should probably verify this theory first? You can instrument the
library to measure how much time it spends to answer stat calls.

FUSE creates a thread per request, reusing threads if possible.
Another possible slowdown is that the FUSE threads run on different
CPUs and contend for shared locks to inspect the in-process inode
tree.

-- 
Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
fuse-devel mailing list
fuse-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fuse-devel
[prev in list] [next in list] [prev in thread] [next in thread]