# HG changeset patch # User Alain Mazy # Date 1697447651 -7200 # Node ID 54bed7c93d6a95a8bf0e6d84ff39a436ebb28a23 # Parent c5f1865aaa3bd83d2ce1e8be70f4d5d826b31aae todo diff -r c5f1865aaa3b -r 54bed7c93d6a TODO --- a/TODO Wed Oct 11 12:41:41 2023 +0200 +++ b/TODO Mon Oct 16 11:14:11 2023 +0200 @@ -41,6 +41,19 @@ https://discourse.orthanc-server.org/t/performance-issue-when-adding-a-lot-of-jobs-in-the-queue/3915/2 Note: that might also be the right time to have a central jobs registry when working with multiple Orthanc instances on the same DB. +* Right now, some Stable events never occurs (e.g. when Orthanc is restarted before the event is triggered). + Since these events are used to e.g. generate dicom-web cache (or update it !), we should try + to make sure these events always happen. + - Generate the events when setting IsStable=true when starting an Orthanc (ok for SQLite) ? + - Also consider the use case of an Orthanc cluster that is being scaled-down just after one Orthanc instance + has received a few instances -> we can not only check for missing stable events at startup since no Orthanc will start. + We would need to maintain the list of "unstable" resources in DB instead of memory only. +* In prometheus metrics, implement Histograms or Exponential Histograms to measure durations. Right now, we only provide + "average" durations that are not very relevant + (https://opentelemetry.io/docs/specs/otel/metrics/data-model/#histogram) + - for job durations (+ have one histogram for each job) + - for HTTP request handling + - ... ============================ Documentation (Orthanc Book) @@ -131,7 +144,6 @@ https://discourse.orthanc-server.org/t/orthanc-convert-ybr-to-rgb-but-does-not-change-metadata/3533/9 * Implement a 'commit' route to force the Stable status earlier. https://discourse.orthanc-server.org/t/expediting-stability-of-a-dicom-study-new-api-endpoint/1684 - --------- Long-term