[c-nsp] Wr mem causes massive delay...

[Tony Varriale]

A large VoIP config isn't what I consider normal for your platform.  As a 
side note, what's typical utilization and what is the utilization when you 
typically make changes?

So, either you can size the platform appropriately or do config management 
during non-biz hours.

So if you wr mem is taking 60 seconds to complete, yes your spike in latency 
through the box is expected.  Conversely, you would always try it with IP 
addressing only and see what you get.

tv
----- Original Message ----- 
From: "Jonathan Charles" <jonvoip at gmail.com>
To: "Seth Mattinen" <sethm at rollernet.us>
Cc: <cisco-nsp at puck.nether.net>
Sent: Monday, January 25, 2010 11:40 AM
Subject: Re: [c-nsp] Wr mem causes massive delay...


> It is a big config... cuz of all the voipy stuff.
>
>
> J
>
> On Mon, Jan 25, 2010 at 11:14 AM, Seth Mattinen <sethm at rollernet.us> 
> wrote:
>
>> On 1/25/10 8:07 AM, Church, Charles wrote:
>> > This is a software based router, and 'wri mem' is very CPU intensive.
>>  What does the CPU look like before the wri mem is done?  I don't think 
>> this
>> is abnormal.
>> >
>>
>> Very large config on an already busy router with compress-config turned 
>> on?
>>
>> ~Seth
>> _______________________________________________
>> cisco-nsp mailing list  cisco-nsp at 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 at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/