Is there something that changed from 2.2 -> 2.4 with regards to the
speed of netstat and /proc/net/tcp? We have some webservers we just
upgraded from 2.2.19 to 2.4.12, and some in-house monitoring tools that
check /proc/net/tcp have begun to suck up a lot of CPU cycles trying to
read that file.
A simple cat or wc -l on the file feels like about on the order of two
magnitudes slower ("time" reports around a second when the file has 450
entries). Some servers seem to be worse than others, and it does not
appear to be proportional to the number of entries across servers.
netstat -tn just crawls along on these servers. Should I enable
profile=1 or something to see what's happening here?
Examples:
2.2.19:
[sroot@marble:/root]# time wc -l /proc/net/tcp
858 /proc/net/tcp
0.000u 0.010s 0:00.01 100.0% 0+0k 0+0io 112pf+0w
2.4.12:
[sroot@pro:/root]# time wc -l /proc/net/tcp
463 /proc/net/tcp
0.000u 0.640s 0:00.64 100.0% 0+0k 0+0io 69pf+0w
Simon-
[ Stormix Technologies Inc. ][ NetNation Communications Inc. ]
[ sim@stormix.com ][ sim@netnation.com ]
[ Opinions expressed are not necessarily those of my employers. ]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Oct 15 2001 - 21:00:40 EST