The Illusive Art of Acquiring A Good Idle-PC Value + Investigating Idlepc idlemax to minimise CPU usage

This article from blog:
http://forum.gns3.net/topic2873.html
http://forum.gns3.net/topic4197.html
Thanks for rednectar.

----------------------------------------------------------------
 The Illusive Art of Acquiring A Good Idle-PC Value
----------------------------------------------------------------

One of the most difficult problems new users have to come to grips with when starting out with GNS3 is the concept of an Idle-PC.

Get it right, and you will have a great GNS3 experience. Try to ignore it, and you will be forever miserable.

Here is my tedious and time consuming method of finding a good idle-pc value.

REPEAT FOR EVERY DIFFERENT IOS IMAGE YOU WISH TO RUN ON YOUR SYSTEM:

How to minimize CPU utilization when using Dynamips/GNS3 (idlepc + idlemax)

This article from blog: http://journeyofanetworkengineer.blogspot.com/2010/12/how-to-minimize-cpu-usage-when-using.html#!/2010/12/how-to-minimize-cpu-usage-when-using.html
Thanks for NE.

And other ref blog is: Drastically decreasing CPU load in Dynamips
http://lostintransit.se/2011/05/16/drastically-decreasing-cpu-load-in-dynamips/

This is my experiment in minimizing the CPU usage when working on GNS3/Dynamips. On this experiment I have use the Internetwork Expert Topology (INE) Version 5 which has 13 routers and uses 3725 IOS images.

If you need the topology just visit INE Website.

http://www.ine.com/resources/iosonpc.htm

GNS3 Show %CDP-4-DUPLEX_MISMATCH

This article from blog: http://myciscolabs.blogspot.com/2011/09/gns3-duplex-mismatch-messages.html
Thanks for Cisco Freak.

When Cisco devices are connected to one another and CDP is enabled (which it is by default), if one port is configured as full duplex but the other is configured as half duplex, the two devices will log "duplex mismatch" messages. This can be very helpful in the real world. However, when using GNS3 these messages can appear for no reason at all, and they will constantly reappear, over and over again. Things get worse when you've got one router connected to two others, as was the case in the example below:

 01:43:20.579: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet1/0 (not half duplex), with R1 FastEthernet0/0 (half duplex).