found it:
see 
http://www.cisco.com/en/US/docs/ios/fundamentals/configuration/guide/config_cache.html

On Tue, Jun 10, 2008 at 1:15 PM, Pavel Skovajsa
<[EMAIL PROTECTED]> wrote:
> Hey,
> The reason why show run consumes high cpu is that it polls all IOS
> modules/componets to get their configs
> I remember there is a command on newest IOS that uses some ram to
> cache show run output and speed the show run output process, but I
> cannot remember the exact command.
>
> Pavel
>
> On Tue, Jun 10, 2008 at 9:36 AM, Saku Ytti <[EMAIL PROTECTED]> wrote:
>> On (2008-06-09 15:56 -0400), Nick Davey wrote:
>>
>> Hey Nick,
>>
>>> I've deployed rancid on a fairly large metro network, and am seeing some
>>> pretty high CPU averages. When RANCID runs the CPU's on a large number of
>>> our boxes spike to about 95% for several seconds. Although they have never
>>> hit 100%, or caused any issues (dropped OSPF hello's, stp bpdu's) I'm
>>> concerned that this could happen under the right combination of events this
>>> could result is dropped OSPF neighbor adjacency's or other badness.
>>
>>  As other already pointed out, you shouldn't worry there is (sucky)
>> scheduler in IOS that'll make sure that your OSPF/STP etc. keeps rocking
>> while doing lower priority stuff, such as what rancid does.
>>  However, if you're running software platform (you prolly aren't, if
>> you have STP) some commands do compete with CEF, such as 'show run'
>> (but not 'show conf' and 'dir'.). And if you have accurate enough
>> monitoring, you can observe slightly increased jitter/latency
>> for few packets transiting eg. VXR when 'show run' or 'dir'
>> is issued.
>>
>> --
>>  ++ytti
>> _______________________________________________
>> cisco-nsp mailing list  cisco-nsp@puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>>
>
_______________________________________________
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Reply via email to