Thanks Kevin.
Here the last minute captured, no more high kqread CPU consumption.
I didn't do any of tuning, just fixing some routes & moving one bgp
session
PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND
2540 root 2 0 223M 220M kqread 350:04 0.98% 0.98% rpd
36068 root 32 0 21736K 824K RUN 0:00 0.00% 0.00% top
rgs
a. r. isnaini rangkayo sutan
Kevin Oberman wrote:
Date: Fri, 15 Aug 2008 11:14:20 +0700
From: "a. rahman isnaini rst / netsoft" <[EMAIL PROTECTED]>
Sender: [EMAIL PROTECTED]
Dear Juners,
Since limited documentation resources, anybody would like to suggest how
can we tune the Engine to get kqread normal ?
And what might cause of this high cpu condition ?
PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND
2540 root 2 0 223M 220M kqread 268:48 44.34% 44.34% rpd
While I can't supply any answer, the thing that is eating up the CPU is
rpd, the main routing daemon. It is reading the kernel queue if it is in
the kqread state.
To see the route processor using 44% of the CPU is rather high. Even on
our core routers I generally only see 3-5% CPU use by rpd. It runs much
higher at time when there is routing instability.
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp
