Last year (in this article) I asserted that monitoring of all user operations on an on-going basis was highly valuable. At the time I was not aware of any automated tools to do this task, meaning that solutions would need to be implemented on a per-application basis. In the worst case, this could mean laboriously adding logging statements into application code and then providing analysis mechanism to extract meaningful information from this logging. Continue reading ‘Monitoring all user interactions’ »
Posts tagged ‘monitor’
A performance model will be full of assumptions and estimates, and yet it is necessary to make important design decisions and capacity choices based on its predictions. This means that it will be necessary to check that it is correct, known as validating the model. Continue reading ‘Validating a performance model’ »
When implementing a new system it is common to make high level assumptions about how the system will be used, based on the information provided by the business community on how they expect the system to be used. This form of input tends to be fairly high level, such as the number of transactions per day that they expect once the system is fully operational. This is a strong start point for working out the likely level of demand that will be placed on the system, which is a process that involves a set of estimates and inferred values in order to arrive at a likely behaviour profile. These figures are then used as the basis for performance and load testing of the system. Consider the future briefly though, since this is also when a little forethought in the specification and design of the original system can deliver a huge benefit. Continue reading ‘How much do you know about your users?’ »
