Re: Replacing loopback with Unix Domain Sockets for I/O

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

 



On Friday, November 6, 2015 1:01:41 PM, Prasanna Kumar Kalever Wrote:
> Hi Prasanna,
> 
> We are already working on a unix domain socket solution instead of  TCP
> loopback connection for communicating between gluster Client and Server.
> At  first the plan was to consider a rpc call (
> http://review.gluster.org/#/c/12489/ , http://review.gluster.org/#/c/12508/)
> issued by client and get the bind address from glusterd.  Because,  in some
> code paths, we use hardcoded 'localhost' to establish the connection which
> cause issues when the gluster is bound to a different address via
> 'transport.socket.bind-addres'.

Humble, I am sure the patches above refer to using Unix Domain sockets for volfile transmission.
My proposal is for I/O between processes on the same hypervisor, specially for hyper-convergence scenario :)

- prasanna


> 
> 
> 
> --Humble
> 
> 
> On Fri, Nov 6, 2015 at 12:38 PM, Prasanna Kumar Kalever <pkalever@xxxxxxxxxx
> > wrote:
> 
> > Hi all,
> >
> > Currently we use TCP loopback connection for communicating between gluster
> > Client and Server.
> > Hyper-convergence may also require communication with a server running in
> > the same hyper-visor.
> >
> > I was initially wondering if replacing IPC  with Unix Domain sockets will
> > improve the performance?
> >                                              Or
> > Is there any theory that proves that Unix Domain socket would give better
> > performance then TCP loopback connection?
> >
> > Finally I have to Say:
> >
> > Yes, local IPC by unix domain sockets will be faster than communication by
> > loopback connections because you have less TCP overhead
> >
> > Postgres core developer Bruce Momjian has blogged @
> > http://momjian.us/main/blogs/pgblog/2012.html#June_6_2012 about this
> > topic. Momjian states, "Unix-domain socket communication is measurably
> > faster." He measured query network performance showing that the local
> > domain socket was 33% faster than using the TCP/IP stack.
> >
> > Found a paper @
> > http://osnet.cs.binghamton.edu/publications/TR-20070820.pdf
> >
> > Also See,
> >
> > http://lists.freebsd.org/pipermail/freebsd-performance/2005-February/001143.html
> > http://bhavin.directi.com/unix-domain-sockets-vs-tcp-sockets/
> >
> >
> > The whole Idea is to bring IPC through Unix Domain Sockets in gluster
> > instead of localhost loopback!
> >
> > Any suggestions will be appreciated!
> >
> > - Prasanna ​
> >
> >
> > _______________________________________________
> > Gluster-devel mailing list
> > Gluster-devel@xxxxxxxxxxx
> > http://www.gluster.org/mailman/listinfo/gluster-devel
> 
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel@xxxxxxxxxxx
> http://www.gluster.org/mailman/listinfo/gluster-devel
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel




[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux