These are collected on two different clouds, one performing many ironic operations constantly as a benchmark, one simply left alone over the weekend. Resets line up with restarting the ironic conductor service, these are stock TripleO deployments with Newton, nothing special required to reproduce.
If you zoom in some it seems to be related to periodic conductor tasks like updating node status.
This dashboard shows a very slight upward trend in average introspection times as the cpu load trends up. About 30 seconds, so you'd be hard pressed to call it a serious performance issue at this point, but if the trend continues over lets say a couple of months it would be concerning.
https:/ /snapshot. raintank. io/dashboard/ snapshot/ S7oMf3rpbynrPK7 U313Xk1WRZMrFg4 ZB
https:/ /snapshot. raintank. io/dashboard/ snapshot/ 63GIebBJWAkAyH5 iI286v6BXqtm4l3 1B
These are collected on two different clouds, one performing many ironic operations constantly as a benchmark, one simply left alone over the weekend. Resets line up with restarting the ironic conductor service, these are stock TripleO deployments with Newton, nothing special required to reproduce.
If you zoom in some it seems to be related to periodic conductor tasks like updating node status.
https:/ /snapshot. raintank. io/dashboard/ snapshot/ Sp2wuk2M5adTpqf XMJenMXcSlCav2P iZ
This dashboard shows a very slight upward trend in average introspection times as the cpu load trends up. About 30 seconds, so you'd be hard pressed to call it a serious performance issue at this point, but if the trend continues over lets say a couple of months it would be concerning.
http:// elk.browbeatpro ject.org: 8080/goto/ 71754b3cba15049 fe7a89a5de30fcf 2d
Credit to rook for the second and third graphs.