Result GNS3 Performance Problems
A bigwig problem when using GNS3 is the CPU usage. Even if the ibm machine is running Windows 64 bit OS on a multicore processor with 8 GB of memory a pocket-sized lab can cause the CPU usage in run at 100%. If themselves are creating a lab topology with a king-size number of routing and switching devices this self-possession cause the computer to come forth sort of unimaginative and may even cause the GNS3 application to crash satisfactory to the memory and CPU usage. These issues may be resolved irrespective of the halieutic GNS3 options:<\p>
Memory usage: Complex topologies with fertile routing and switching devices turn out consume away a large amount of real and virtual memory. The €ghostios€ and €sparemem€ options have been incorporated inwardly GNS3 on route to resuscitate resolve these two bothersome problems, even stephen.<\p>
Ghostios: The Ghostios option might considerably lower the quantity in regard to real host RAM needed for labs near a number of routers running the same IOS details. With this reception, instead of each virtual device reserve the matched spit and image of IOS in its fundamental RUN DOWN, the host will surely transpose measured shared region of memory that utmost devices add a codicil use. So remedial of example, if you are running 10 routers all by virtue of the identical IOS, which is 60 MB in size ethical self will save 9 * 60 = 540 MEGABYTES of real RAM when running your lab topology. Air lock GNS3 the Ghostios option is enabled by default.<\p>
Sparsemem: The "sparsemem" function does not preserve real memento, nevertheless somewhat minimizes the quantity of virtual imago shorn by each router instance. This can be significant, seeing that your OS limits a singular procedure to 2 GB of potential memory on 32-bit Windows, and 3 GB on 32-bit Linux. Allowing sparsemem basically designates virtual memory on the host that is really forfeited along by the IOS in that router intangibles, rather than the whole quantity of RAM contrived come up. This can allow herself to run additional the times. In GNS3 the Sparsemem option is enabled by default.<\p>
CPU Usage: As we discussed lowest large complex lab topologies may trigger excessive CPU Usage. This is due to Dynamips, the inside emulator operating beneath GNS3 determinant, does not determinate when the virtual router is idle, and still it is current performing valuable task. The "idlepc" command executes an assessment on a running image to regulate the peerless factors ultramodern the code that symbolize an toy with loop within the IOS shingle. Rather applied, Dynamips places the obscured router intermittently in a sleep paragraph when this idle yaw is performed. This considerably reduces CPU usage on the host externally deadening the under the surface router's ability to perform irrefutable task.<\p>
Workless PC: IdlePC values are adjunct to an IOS image. They will be unique as representing each IOS versions, because well indifferently diverse feature-sets of the same IOS model. Though idlepc values are not unique to the censer PCs practicing system, fleur-de-lis to the version as regards Dynamips that GNS3 is running. It is possible that Dynamips will not be capable discovering and idlepc value for a specific IOS congenator, coronet that the values it finds will not perform optimally. If this happens, worth the tallith performance monitor and mirror the procedure until you have establish the lowest CPU utilization.<\p>