If TrafficServer does seem to be spending a lot of CPU time simply writing data to the network, one thing some people have had luck with in the past is simply to enable application-level buffering.
See the documentation, the settings for that are: proxy.config.net.sock_recv_buffer_size_in proxy.config.net.sock_send_buffer_size_in proxy.config.net.sock_recv_buffer_size_out proxy.config.net.sock_send_buffer_size_out Hope this helps. Regards, Adam On Wed Jan 07 2015 at 6:11:53 AM Daniel Biazus <[email protected]> wrote: > Hi Guys, > > We have been facing a very similar issue. I got this with with perf top > tool: > > 88.18% traffic_server [.] _Z15write_to_net_ > ioP10NetHandlerP18UnixNetVConnectionP7EThread > 0.32% traffic_server [.] _ZN10NetHandler12mainNetEventEiP5Event > 0.30% [kernel] [k] update_sd_lb_stats > 0.29% [e1000e] [k] e1000e_check_ltr_demote > 0.25% [kernel] [k] __ticket_spin_lock > 0.24% traffic_server [.] _ZN7EThread13process_eventEP5Eventi > 0.21% [kernel] [k] timerqueue_add > 0.17% libc-2.12.so [.] epoll_wait > 0.17% libpcre.so.0.0.1 [.] 0x00000000000100dd > 0.14% [kernel] [k] __schedule > > Any thoughts ? > > Best Regards, > Daniel Biazus > > > On Tue, Jan 6, 2015 at 10:36 PM, Jason J. W. Williams < > [email protected]> wrote: > >> Thanks Sudheer. I was thinking maybe there was some built-in >> instrumentation that would help. During the spikes all perf shows me >> as the top calls are: >> >> 9.79% [kernel] [k] _raw_spin_lock >> 9.44% [kernel] [k] find_busiest_group >> >> Which isn't very helpful. >> >> -J >> > > > > -- > > Daniel Biazus > infrastructure Engineering > Azion Technologies > Porto Alegre, Brasil +55 51 3012 3005 | +55 51 82279032 > Miami, USA +1 305 704 8816 > > Quaisquer informações contidas neste e-mail e anexos podem ser > confidenciais e privilegiadas, protegidas por sigilo legal. Qualquer forma > de utilização deste documento depende de autorização do emissor, sujeito as > penalidades cabíveis. > > Any information in this e-mail and attachments may be confidential and > privileged, protected by legal confidentiality. The use of this document > require authorization by the issuer, subject to penalties. > >
