we do normally warm up the systems and concerned about the how it performs under load but will it meet customer expectation or improve customer experience or avoid frustrating scenarios ?
how about the 'first time' and idle case performances ?
did you ever check what is the single user response times and request processing times on server side ? if it is not performing any good for single user then it will not do for multiple. The base performance for single user is what needs to tuned first
what about first time cases ? we can not ask users of the system to hang on until system warms up ! then who will use it first :) so, analysing cold case system performance is important. it is important to know what happens on first access across the layers in cold cases i.e. after a system restart, app servers or entire VMs or DB etc., and what needs to be tweaked to get better first time performance.
how about sleeping systems ! not all systems work round the clock atleast not all days in a week.. so did you ever check what is the resource usage of idle systems ? there could be some unexpected code path executions might happen even under no load case. So it is important to know the resources usage under no load as they might also run all the time.
how about apps performance under a very slow network access or networks with high packet loss. how reliable are the systems..
what happens when infrastructure fails ? how many users can still continue doing what ever they are doing with out any interruption and feel the same performance of the app while a DR process kicks in..
how about the systems with long running sessions.. users may not logout for long time and it is required to keep the sessions so long and what is the impact !
how the applications handle when majority of end users do not logout but just closes the browser ! how to handle the memory usage in those cases..
No comments:
Post a Comment