3 years ago #amazon, #loadtest, #oracle, #performance, #stresstest
Great to have you back all :smile: PerfBytes Prooving Performing Performance Puns is Pretty Popular at least with Priceless Points for im-Provement. :smile:
Did you ever talk about the CEll Outage after Michael? or other performance issues due to Florence (other major storms?)
(A budget to go to a couple conferences a year would be an awesome perk bonus) :smile:
No no shoes I did get an awesome perfbytes stopwatch that I still use
Exploratory performance testing absolutely.. #LivingInTheWaterfall
One more thing people should consider. Autoscalling does not fix everything, What's more, if you aren't writing and maintaining Scripts for setup and deployment of machines, as well as deployment of code when updates come, the 'drift' of configurations over time will become a real nightmare to try and track down issues when you get performance and load conditions.
(I wouldn't characterize myself as a 'Performance Guru' not when we have people like Paul, James, Mark, and maybe Andy in the room. Perhaps Performance infected?)
Splunk btw is an awesome tool in both prod and test environments.
The critical path dependency in Lazy loading apps, is only as good as the next critical script to run. So true.
It's nearly identical to the the problem of multiple empty carts being built up and never being disposed of problem
I just read they added an exit option so that might help that problem now