Re: POHMELFS high performance network filesystem. Transactions, failover, performance.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, May 15, 2008 at 02:41:33AM +0400, Evgeniy Polyakov (johnpol@xxxxxxxxxxx) wrote:
> > This is the core reason why I am so interested in distributed storage... 
> >  a single storage device is usually slower than network wire speed. 
> > Multiple nodes helps remove that limitation and max out the network.
> > 
> > I want to be able to stream data _faster_ than a single hard drive can 
> > handle :)
> 
> In that case yes, network will _not_ be saturated and multiple
> simultaneous streams will have a win, but POHMELFS client design was
> specially created to increase network performance as much as possible,
> since we can increase storage speed (add more drives, more RAM
> for caches, better hardware), but can not easily increase network
> bandwidth.

Actually experiments with async processing in POHMELFS lead to the
conclusion, that if protocol waits until request is completed and does
not proceed with the next one (like CIFS and somewhat NFS), such design
does not scale to multiple parallel IOs.
That from different angle shows benefits of caching and aiming at
getting as much performance as possible from single node connection :)

-- 
	Evgeniy Polyakov
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux