Timeline for Can a proportionately scaled down testing environment find performance load issues?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 6, 2017 at 12:15 | history | edited | Michael Durrant | CC BY-SA 3.0 |
deleted 1 character in body
|
| Mar 12, 2016 at 21:53 | comment | added | Alexandre Martins | Sorry. I meant to compare the changes in a scaled down testing environment before and after applying them. We already do it for production but that is already too late. | |
| Mar 12, 2016 at 21:30 | history | edited | Michael Durrant | CC BY-SA 3.0 |
added 498 characters in body
|
| Mar 12, 2016 at 21:27 | comment | added | Michael Durrant | Yes, you could monitor the live production performance over time and that would help you monitor spikes and issues. A lot of the applications that monitor server performance have charts that display it. You'll at least know how performance handles your current peaks and you'll be able to do useful before and after change comparisons to see if recent changes have affected it a lot. It's kinda late in the development cycle but better than nothing. Added this to the answer. | |
| Mar 12, 2016 at 21:12 | comment | added | Alexandre Martins | I am not assuming there are no other factors or that the scaling is linear in any way. But the system is already in production and as been running along for many years. When I read your answer, I started wondering if we could compare the performance before after the changes. The comparison might be good enough to raise alarm bells before further investigation. I wonder if that would work? | |
| Mar 11, 2016 at 22:46 | history | answered | Michael Durrant | CC BY-SA 3.0 |