Mercurial > hg > orthanc-book
comparison Sphinx/source/faq/scalability.rst @ 188:60c91045bf2a
cont
author | Sebastien Jodogne <s.jodogne@gmail.com> |
---|---|
date | Thu, 31 Jan 2019 19:13:52 +0100 |
parents | 0fa1cf88c635 |
children | da12a1d08eb6 |
comparison
equal
deleted
inserted
replaced
187:0fa1cf88c635 | 188:60c91045bf2a |
---|---|
4 ====================== | 4 ====================== |
5 | 5 |
6 One of the most common question about Orthanc is: *"How many DICOM | 6 One of the most common question about Orthanc is: *"How many DICOM |
7 instances can be stored by Orthanc?"* | 7 instances can be stored by Orthanc?"* |
8 | 8 |
9 The source code of Orthanc imposes no such hard limit by itself. The | 9 The source code of Orthanc imposes no such hard limit by itself. At |
10 stress is actually put on the underlying database engine, and on the | 10 the time of writing, we know that Orthanc is being used in production |
11 storage area (check out :ref:`orthanc-storage`). As explained in the | 11 in hospitals with more than 15TB of data, 125,000 studies and around |
12 :ref:`troubleshooting section <troubleshooting>`, the built-in SQLite | 12 50 millions of instances (please `get in touch with us |
13 database engine should be replaced by an enterprise-ready database | 13 <https://www.orthanc-server.com/static.php?page=contact>`__ if you can |
14 engine as soon as the number of DICOM instances grow above about | 14 share other testimonials). |
15 50,000 (check out the :ref:`postgresql` and :ref:`mysql`). It is also | 15 |
16 true that the performance of Orthanc in the presence of large | 16 The stress is actually put on the underlying database engine, and on |
17 databases has continuously improved over time, especially when it comes | 17 the storage area (check out :ref:`orthanc-storage`). As explained in |
18 to the speed of :ref:`DICOM C-FIND <dicom-find>`. | 18 the :ref:`troubleshooting section <troubleshooting>`, the built-in |
19 SQLite database engine should be replaced by an enterprise-ready | |
20 database engine once Orthanc must store several hundreds of thousands | |
21 of DICOM instances (check out the :ref:`postgresql` and | |
22 :ref:`mysql`). It is also true that the performance of Orthanc in the | |
23 presence of large databases has continuously improved over time, | |
24 especially when it comes to the speed of :ref:`DICOM C-FIND | |
25 <dicom-find>`. | |
19 | 26 |
20 Here is a generic setup that should provide best performance in the | 27 Here is a generic setup that should provide best performance in the |
21 presence of large databases: | 28 presence of large databases: |
22 | 29 |
23 * Make sure to use the latest release of Orthanc (1.5.3 at the time of | 30 * Make sure to use the latest release of Orthanc (1.5.3 at the time of |
27 <postgresql>` to store the database index (3.0 at the time of | 34 <postgresql>` to store the database index (3.0 at the time of |
28 writing). Make sure that ``EnableIndex`` is set to ``true``. | 35 writing). Make sure that ``EnableIndex`` is set to ``true``. |
29 | 36 |
30 * Make sure that :ref:`run-time debug assertions <troubleshooting>` | 37 * Make sure that :ref:`run-time debug assertions <troubleshooting>` |
31 are turned off. A warning will show in the logs if this is not the | 38 are turned off. A warning will show in the logs if this is not the |
32 case. | 39 case. Note that all pre-built binaries provided by Osimis are |
40 correctly configured in that respect. | |
33 | 41 |
34 * We suggest to use the default filesystem storage area. Of course, | 42 * We suggest to use the default filesystem storage area. Of course, |
35 make sure that the filesystem is properly backup, and that | 43 make sure that the filesystem is properly backup, and that |
36 technologies such as RAID are enabled. Make sure that the option | 44 technologies such as RAID are enabled. Make sure that the option |
37 ``EnableStorage`` of the PostgreSQL plugins is set to ``false``. | 45 ``EnableStorage`` of the PostgreSQL plugins is set to ``false``. |