Date: Thu, 21 Jan 2016 14:42:40 -0800 From: Adrian Chadd <adrian.chadd@gmail.com> To: Matthew Macy <mmacy@nextbsd.org> Cc: Ryan Stone <rysto32@gmail.com>, "<freebsd-transport@freebsd.org>" <freebsd-transport@freebsd.org> Subject: Re: Flamegraph of 8KB message bottlenecks Message-ID: <CAJ-VmometVvTP1GDffDDnGChLC6TFYDz=E5-vXd2wexHd9cDLw@mail.gmail.com> In-Reply-To: <1526652dd58.117a1e7e938176.477104883701987065@nextbsd.org> References: <CAFMmRNzBfNB7Fr3VYKJwHpxt1CBc4gT6Yh%2Bqx2u2O_K1KF3nxQ@mail.gmail.com> <CAJ-Vmo=CLt7xL04pTRui-qdsSeugsHqu3pCOYOKQT-mARPfEkg@mail.gmail.com> <1526652dd58.117a1e7e938176.477104883701987065@nextbsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 21 January 2016 at 14:34, Matthew Macy <mmacy@nextbsd.org> wrote: > ~170k interrupts / second for ~800kpps, but at this point clearly all the time is spent on syscall overhead Sure, that's why I asked. I see the fgets stuff looking lock contend-y, and I see a sleeplock kicking in via kern_sendit -> sx_xlock_hard; so something's blocking on a lock. The kqueue locking too is a problem - kqueue doesn't handle lots of fast producer/consumer things and it contends badly. :( -a > > > > ---- On Thu, 21 Jan 2016 14:11:34 -0800 Adrian Chadd <adrian.chadd@gmail.com> wrote ---- > > Well, how many interrupts/second is this seeing? > > > > > > -a > > _______________________________________________ > > freebsd-transport@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-transport > > To unsubscribe, send any mail to "freebsd-transport-unsubscribe@freebsd.org" > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmometVvTP1GDffDDnGChLC6TFYDz=E5-vXd2wexHd9cDLw>