This adds a new profiling event called DISCONNECT_WAIT, which measures the time between the moment we close our ports, and the moment the corresponding ClosePort messages have been picked up by our peers and we can continue to shut down. Previously, the component showed as running during this time in the timeline plot, which is not correct, it's waiting.
The plotting code has been adapted to use it when available, and the database format version is incremented to 1.1. Version 1.0 databases remain supported, but will continue to give the old incorrect results.
This also adds a new example of a three-component dispatch chain, which produces nice test data, and fixes a bug with the timeline plot in case the database is small enough that we'll never have a data cutoff.
This adds a new profiling event called DISCONNECT_WAIT, which measures the time between the moment we close our ports, and the moment the corresponding ClosePort messages have been picked up by our peers and we can continue to shut down. Previously, the component showed as running during this time in the timeline plot, which is not correct, it's waiting.
The plotting code has been adapted to use it when available, and the database format version is incremented to 1.1. Version 1.0 databases remain supported, but will continue to give the old incorrect results.
This also adds a new example of a three-component dispatch chain, which produces nice test data, and fixes a bug with the timeline plot in case the database is small enough that we'll never have a data cutoff.
Addresses #254.