{"id":16731,"date":"2022-02-03T20:15:17","date_gmt":"2022-02-03T14:45:17","guid":{"rendered":"https:\/\/cigniti.com\/blog\/?p=16731"},"modified":"2022-02-03T21:34:55","modified_gmt":"2022-02-03T16:04:55","slug":"performance-testing-go-live","status":"publish","type":"post","link":"https:\/\/www.cigniti.com\/blog\/performance-testing-go-live\/","title":{"rendered":"Performance testing before go-live a worthwhile practice?"},"content":{"rendered":"

Is Performance testing before go-live a worthwhile practice?<\/p>\n

For every performance testing professional and purists out there that have been religiously practicing proactive performance testing before go-live, is this not a sacrosanct question?<\/p>\n

And we can expect that they would invariably react by letting us know of numerous examples in the past of how they have been able to proactively identify performance issues before go-live that resulted in better utilization of hardware and improved customer experience. Over and above, how they have managed to protect the brand from being tarnished, or it might also be improved sales as examples of benefits due to this proactive approach.<\/p>\n

Of course, the benefits of proactive performance initiatives far outweigh when compared to practices of \u201cthrowing more hardware to solve application performance problems\u201d but how relevant is this practice in the age of<\/p>\n