I have been spending a lot of time focused on the HyPerformix modeling tool, IPS Optimizer. I have been demonstrating what I know about the tool to many diverse individuals. The tool rapidly provides an "ah ha" to many. The Modeler component shows off the Wysiwig topology interface of a system model. Behind the covers is the "ADN" code that makes the discrete simulation model work. When completed, the model visually contains what I call plug-and-play calibrated components (routers, firewalls, app servers, db servers, mainframes, etc) that can be clicked and modified. This allows for rapid changes to simulation runs to answer the business or technical what-if questions.
Behind the GUI is the simulation code. Best practice is to let the Application Model Generator generate the code from the parameters that are entered on the AMG worksheet. These parameters associate
- transactions to business scenarios
- sub-transactions to transactions
- transactions to sub-systems
- sub-systems to servers
and
utilized capacity of the infrastructure to each of the lowest layer of transactions defined.
It is the association of real information on the relationship between transactions and resource consumption that makes the model tick and allows you to modify the model for the implementation that you are considering for production.
1 comment:
Just wanted to clarify that a sub-system is a group of processes on a server that processes transactions. For a web server, it can be one httpd process. In the simulator (i.e. HyPerformix IPS Optimizer), one can specify the maximum number of the web server processes that can run simultaneously.
Post a Comment