You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Zhao Yongming (JIRA)" <ji...@apache.org> on 2013/08/02 16:37:48 UTC
[jira] [Created] (TS-2089) one log collation thread is not enough
for busy system
Zhao Yongming created TS-2089:
---------------------------------
Summary: one log collation thread is not enough for busy system
Key: TS-2089
URL: https://issues.apache.org/jira/browse/TS-2089
Project: Traffic Server
Issue Type: Improvement
Components: Logging
Reporter: Zhao Yongming
we should make log collation more thread & cpu nice.
{code}
top - 22:34:22 up 3:37, 1 user, load average: 1.20, 1.71, 1.66
Tasks: 979 total, 2 running, 977 sleeping, 0 stopped, 0 zombie
Cpu(s): 3.5%us, 0.6%sy, 0.0%ni, 95.6%id, 0.0%wa, 0.0%hi, 0.3%si, 0.0%st
Mem: 65943744k total, 62536348k used, 3407396k free, 90544k buffers
Swap: 2097144k total, 0k used, 2097144k free, 54189788k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
4651 ats 20 0 12.9g 5.3g 4928 R 100.1 8.5 197:51.78 [LOGGING]
4460 ats 20 0 12.9g 5.3g 4928 S 7.9 8.5 18:12.57 [ET_NET 44]
4457 ats 20 0 12.9g 5.3g 4928 S 5.3 8.5 7:32.34 [ET_NET 41]
4461 ats 20 0 12.9g 5.3g 4928 S 4.3 8.5 6:41.79 [ET_NET 45]
4453 ats 20 0 12.9g 5.3g 4928 S 3.0 8.5 6:44.52 [ET_NET 37]
4463 ats 20 0 12.9g 5.3g 4928 S 3.0 8.5 7:54.01 [ET_NET 47]
3652 root 39 19 0 0 0 S 1.0 0.0 2:14.15 kipmi0
4425 ats 20 0 12.9g 5.3g 4928 S 0.7 8.5 0:19.21 [ET_NET 9]
4426 ats 20 0 12.9g 5.3g 4928 S 0.7 8.5 0:19.42 [ET_NET 10]
4430 ats 20 0 12.9g 5.3g 4928 S 0.7 8.5 0:19.55 [ET_NET 14]
132 root 20 0 0 0 0 S 0.3 0.0 0:00.82 events/1
4417 ats 20 0 12.9g 5.3g 4928 S 0.3 8.5 0:19.82 [ET_NET 1]
4418 ats 20 0 12.9g 5.3g 4928 S 0.3 8.5 0:20.02 [ET_NET 2]
4420 ats 20 0 12.9g 5.3g 4928 S 0.3 8.5 0:19.64 [ET_NET 4]
4422 ats 20 0 12.9g 5.3g 4928 S 0.3 8.5 0:19.84 [ET_NET 6]
4427 ats 20 0 12.9g 5.3g 4928 S 0.3 8.5 0:19.94 [ET_NET 11]
4435 ats 20 0 12.9g 5.3g 4928 S 0.3 8.5 0:19.88 [ET_NET 19]
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira