1) Put back all the logging via (Log4j or whatever)
2) Add filters (or whatever) to to all the individual pieces which make up
the entire transaction
3) find the component which is slowest or from a timing point of view
potentially too slow and start attcking that point. For example
- if the database section is too slow - get help from a DBA
- if the xml processing is too slow - check if your parser can be upgraded to
something faster
- if other processing is too slow - use a profiler for the JVM and the OS
- if other processing is too slow - replace the "slow" server with one with a
faster CPU
- If the transaction is across a large distance (many Internet hops) - using
a middle mile accelerator such as Netli or Akamai. (Or rent a dedicated line)
- ...
- Tim
mukesh wrote:
Hi friends,
Got to optimize a system, flow is explained below
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
