Mercurial > hg > orthanc
comparison TODO @ 5727:843973a0fdfa
todo
author | Alain Mazy <am@orthanc.team> |
---|---|
date | Mon, 22 Jul 2024 15:55:36 +0200 |
parents | 13b1ff603b37 |
children | ead98edd5bbf |
comparison
equal
deleted
inserted
replaced
5687:13b1ff603b37 | 5727:843973a0fdfa |
---|---|
39 - Modifying a study while keeping its original StudyInstanceUID: This should be avoided! | 39 - Modifying a study while keeping its original StudyInstanceUID: This should be avoided! |
40 * Store the job registry in a dedicatd table in DB ? | 40 * Store the job registry in a dedicatd table in DB ? |
41 https://discourse.orthanc-server.org/t/performance-issue-when-adding-a-lot-of-jobs-in-the-queue/3915/2 | 41 https://discourse.orthanc-server.org/t/performance-issue-when-adding-a-lot-of-jobs-in-the-queue/3915/2 |
42 Note: that might also be the right time to have a central jobs registry when working | 42 Note: that might also be the right time to have a central jobs registry when working |
43 with multiple Orthanc instances on the same DB. | 43 with multiple Orthanc instances on the same DB. |
44 Note: the json serialization of a job "content" can be very large -> compress it before saving it to DB ? | |
44 * Right now, some Stable events never occurs (e.g. when Orthanc is restarted before the event is triggered). | 45 * Right now, some Stable events never occurs (e.g. when Orthanc is restarted before the event is triggered). |
45 Since these events are used to e.g. generate dicom-web cache (or update it !), we should try | 46 Since these events are used to e.g. generate dicom-web cache (or update it !), we should try |
46 to make sure these events always happen. | 47 to make sure these events always happen. |
47 - Generate the events when setting IsStable=true when starting an Orthanc (ok for SQLite) ? | 48 - Generate the events when setting IsStable=true when starting an Orthanc (ok for SQLite) ? |
48 - Also consider the use case of an Orthanc cluster that is being scaled-down just after one Orthanc instance | 49 - Also consider the use case of an Orthanc cluster that is being scaled-down just after one Orthanc instance |