![]() ![]() Verify that no other code/features have regressed since last time and in general look for further issues.Verify the fixes made for the issues discovered in the previous experiment in the live production environment.The purpose of this second no-downtime experiment is at least four-fold: And now another no-downtime experiment is being planned for September 9. Nevertheless, I wanted to start this blog with a concrete example of improvements made in downtime reduction since last time. ![]() Downtime will not become much less than 160-200 seconds instead there must first be fewer downtimes and then none at all. There is a (soft) lower bound of approximately 3 minutes given the three different activities during downtime - shutdown, database jobs, startup - which last approximately 1 minute each, unless fundamental changes are made, and the most fundamental one is still to not have any downtime at all. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |