As a result, a single database
call may result in tens of thousands of function calls and database accesses. Such an application
will usually not scale well; as more users are added to the system, the CPU burden of the number
of executions per user will slow the performance for the individual users. Tuning the individual
SQL statements executed as part of that application may yield little performance benefit; the
statements themselves may be well-tuned already. Rather, it is the sheer number of executions
that leads to the performance problem.
The following best practices may seem overly simplistic, but they are violated over and over
in database applications, and those violations directly result in performance problems. There are
always exceptions to the rules??”the next change to your software or environment may allow you
to violate the rules without affecting your performance. In general, though, following these rules
will allow you to meet performance requirements as the application usage increases.
Do As Little As Possible
End users do not care, in general, if the underlying database structures are fully normalized to
Third Normal Form or if they are laid out in compliance with object-oriented standards. Users
want to perform a business process, and the database application should be a tool that helps that
M
Chapter 5: Developing and Implementing Applications 125
business process complete as quickly as possible.
Pages:
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226