Finding software instability by graphing health measures by minute Checking for Chaos – Spikes in Software Response Times. ©2020 iiSM.ORG, All Rights Reserved. Check Minute Trends for Unexpected Spikes. 3a. Minutely Measures are great for detecting the presence of software instability
Check for unexpected spikes in minutely averages that are 2X larger than normal. Common causes of software Latency Spikes:
Over used or poor performing disk, network, etc.
Large payloads over slow networks
Large table scans or poor performing queries
Using retries to ‘solve’ an unknown problem
Missed events or errors that result in timeouts
Faulty resource locking and lock escalations
Large spin-up or tear-down costs at execution or connection time. Click slide to see in context of slide deck
Click to enter the site

Our mission is to strengthen the careers of software leaders by sharing as much software management theory, research and knowledge as humanly possible. We encourage you to join the mission by using our materials for personal growth, sharing among friends, and mentoring within your company; however, commercial training use must be licensed.

Our Funding model is to: provide certification and live training services as desired and requested by our community. We do this so that our staff can buy pop tarts, pay their bills, and produce more career boosting content, research and tools.

We require that our copyright notices are left in place.