Pod Status Update Latency Comparison Between Builds

6th chunk of `content/en/blog/_posts/2016-11-00-Visualize-Kubelet-Performance-With-Node-Dashboard.md`

21fea5bb3b418dc5eed7cf6890ac94e5487b5178e05361000000000100000307

![](https://lh3.googleusercontent.com/_8y02WcgZ7ETvDTeZ893rZYNuIR2j32_jnl7O1Mj3cP9Y7I3C-gegDgSdYX1VtTpGDUo6JEouueSj8hGWPJSXj_5GcC9nE21tjIXgTIrwRXW-0jYpXdRh6oDSSdQ1XKPyXIf3yQu) |
| Figure 5. Time series page using data from build #162. |


Further, by comparing the time series data of build #162 (Figure 5) and build #173 (Figure 6), we find that the performance pod startup latency fluctuation actually happens during updating pod statuses. Build #162 has several straggler "pod\_status\_running" events with a long latency tails. It thus provides useful ideas for future optimization.&nbsp;  



| ![](https://lh5.googleusercontent.com/51IY9sNPEdtEe-HGz75Q4ggt73ngE0p9gsq6B0m6RDJ13MklYZ3s6xREFhWIxwJt0zFBiY6BvDHwLZ57G9UARfXy1wcAb1DwD48poUrXFHgcRVXUe3tfCoCSpZ477NGTA3A8Njrg)

Title: Pod Status Update Latency Comparison Between Builds

Summary

Comparing time series data from builds #162 and #173 reveals that pod startup latency fluctuations occur during pod status updates. Build #162 shows several delayed "pod_status_running" events with extended latency tails, providing insights for potential future optimizations.