[c-nsp] Something I was thinking about whilst idle the other day.

[Phil Bedard]

As far as the CPU jumping to a high amount, that's not necessarily a  
bad thing.  A lot of people think just because a CPU is 99% utilized  
that's a bad thing, when it's not.  It's only bad if the process using  
it is starving other processes from doing their job correctly (icmp  
echo is not an important job).   If I'm paying for the CPU, and it has  
spare capacity, it should be utilized.

Honestly, there are fairly large architecture differences between the  
various platforms, so I've had different issues with different  
platforms.  They still haven't made a platform for me that is perfect  
for all situations, but neither has any other vendor.  Route table  
sizes are constrained by memory and...you have memory on every platform.

Phil

On Mar 19, 2008, at 2:20 PM, Drew Weaver wrote:

>                What are some persistent things about Cisco products  
> that no matter how high into the product line you travel you cannot  
> get away from? I was sitting around the other day thinking about how  
> odd it is that in 2008 the BGP scanner still causes the CPU  
> utilization to jump ridiculously high (on pretty much all routers  
> I've seen..from 7200 to 128xx), and all of the various limitations  
> of the route table sizes in various Cisco products. I realize these  
> issues are either harmless or explainable ("just the way it is") I  
> just think it is a strange/interesting thing to note that years  
> later the same issues are still present in technology no matter how  
> far up you go in the line.
>
>                Not sure what prompt these things in my head :D
>
> -Drew
>
> _______________________________________________
> 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/