I have noticed the following strange behavior: Once the number of origin connections start to increase and the proxying speed collapses the first core is at 100% utilization while the others are not even close to that. It seems like the origin requests are handled by the first core only. Is this expected behavior that can be changed by editing the configuration or is this a bug?
2013/3/20 Philip <[email protected]> > Hi, > > I am running ATS on a pretty large server with two physical 6 core XEON > CPUs and 22 raw device disks. I want to use that server as a frontend for > several fileservers. It is currently configured to be infront of two > file-servers. The load on the ATS server is pretty low. About 1-4% disk > utilization and 500Mbps of outgoing traffic. > > Once I direct the traffic of the third file server towards ATS something > strange happens: > > - The number of origin connection increases continually. > - Requests that hit ATS and are not cached are served really slow to the > client (about 35 kB/s) while requests that are served from the cache are > blazingly fast. > > The ATS server has a dedicated 10Gbps port that is not maxed out, no CPU > core is maxxed, there is no swapping, there are no error logs and also the > origin servers are not heavy utilized. It feels like there are not enough > workers to process the origin requests. > > Is there anything I can do to check if my theory is right and a way to > increase the number of origin workers? > > Best Regards > Philip >
