Fig. 11.1.11 Accessing a lot of data in a single transaction.What happens if one of these long-running programs is mixed with a lot of short-running
programs, as seen in Fig. 11.1.12?
Fig. 11.1.12 Having one transaction that looks at a lot of data disrupts response
time for everyone else.The answer is performance for the entire system comes to a halt. The minute the long-
running program goes into execution, the queue builds behind the long-running program.
And that defeats the purpose of the operational environment.
So what can the analyst do if it is necessary to run a long-running program (which is a
fact of life)?
Fig. 11.1.13 shows some solutions to allowing the system to run long-running programs
and to have online transaction response time.
Chapter 11.1: Operational Analytics: Response Time