| Prev | Next | Start of Chapter | Next Chapter | Contents | Glossary | Index | Comments | (5 out of 5)

Detecting and Preventing Memory Overload

Your application can overload for any number of reasons. The indicators are slowness and intermittent variable failures. You can detect overload in your application by:

Using G2 meters to measure performance
Switching between real time, simulated time, and as fast as possible time, and comparing the current G2 time with the current real time
Creating readouts that give the count of the number of instances of each root class to determine which class is growing
Enabling rule highlighting and using the Inspect facility to show all rules to see which rules are running most often
Showing the count of each procedure invocation to see if the number is growing, identifying the offending procedure, and editing the procedure to abort all procedure invocations

If overload persists after you have addressed these issues:

Explore ways to improve performance by following the guidelines in Chapter 10, Maximizing Performance.
Use G2 Gateway to filter some of the data it is sending to G2.
Consider distributing your application through a network to other G2s by using G2-to-G2 communications.
Port to a more powerful machine.

| Prev | Next | Start of Chapter | Next Chapter | Contents | Glossary | Index | Comments | (5 out of 5)

Copyright © 1997 Gensym Corporation, Inc.