I have seen this before with networking on Xen. Basically, the ethernet nic interrupts are pinned to a single CPU. This is typically a problem with the way the driver interacts with the hardware. ATS is spreading the load, but because most of the work is in TCP/IP and packet processing, the single CPU context handling those functions is the bottleneck. The other CPUs are all mostly idle because they are sharing the other 50% of the work between them.
On Wed, Aug 7, 2013 at 8:41 AM, Brian Geffon <[email protected]> wrote: > Interesting, traffic server creates a ton of threads so it should > definitely distribute across cores unless there is something forcing > affinity. > > On Aug 7, 2013, at 8:34 AM, Noam Schiff <[email protected]> wrote: > > It's not that I see only 1 core on top, I see 8 but only 1 is utilized > On Aug 7, 2013 6:30 PM, "Brian Geffon" <[email protected]> wrote: > >> Try Shift + H in top. >> >> Brian >> >> On Aug 7, 2013, at 7:14 AM, Noam Schiff <[email protected]> wrote: >> >> > Hi, >> > >> > I'm running thousands of transactions per seconds through the >> trafficserver but I apperantly only 1 core is really working hard while all >> the other are pretty idle. >> > I saw the process ET_NET_0 consumes around 70 of the CPU (which I >> assume that this process is being handled by the only core who actually >> working hard). >> > >> > My question is how can I make the trafficserver uses more cores (I >> assume that I need to create more process like this...maybe ET_NET_1, >> ET_NET_2???) >> > >> > I changed the below line from 2 to 8 in "records.config" file but it >> doesn't do the trick: >> > CONFIG proxy.config.exec_thread.limit INT 8 (the default is 2) >> > >> > Any thoughts? >> >
