# HG changeset patch # User Sebastien Jodogne # Date 1548958432 -3600 # Node ID 60c91045bf2a3f65c10a7e1724b01109c4f5a310 # Parent 0fa1cf88c635398f48ffd22fb67bbcfab31c99a3 cont diff -r 0fa1cf88c635 -r 60c91045bf2a Sphinx/source/faq/scalability.rst --- a/Sphinx/source/faq/scalability.rst Thu Jan 31 18:55:58 2019 +0100 +++ b/Sphinx/source/faq/scalability.rst Thu Jan 31 19:13:52 2019 +0100 @@ -6,16 +6,23 @@ One of the most common question about Orthanc is: *"How many DICOM instances can be stored by Orthanc?"* -The source code of Orthanc imposes no such hard limit by itself. The -stress is actually put on the underlying database engine, and on the -storage area (check out :ref:`orthanc-storage`). As explained in the -:ref:`troubleshooting section `, the built-in SQLite -database engine should be replaced by an enterprise-ready database -engine as soon as the number of DICOM instances grow above about -50,000 (check out the :ref:`postgresql` and :ref:`mysql`). It is also -true that the performance of Orthanc in the presence of large -databases has continuously improved over time, especially when it comes -to the speed of :ref:`DICOM C-FIND `. +The source code of Orthanc imposes no such hard limit by itself. At +the time of writing, we know that Orthanc is being used in production +in hospitals with more than 15TB of data, 125,000 studies and around +50 millions of instances (please `get in touch with us +`__ if you can +share other testimonials). + +The stress is actually put on the underlying database engine, and on +the storage area (check out :ref:`orthanc-storage`). As explained in +the :ref:`troubleshooting section `, the built-in +SQLite database engine should be replaced by an enterprise-ready +database engine once Orthanc must store several hundreds of thousands +of DICOM instances (check out the :ref:`postgresql` and +:ref:`mysql`). It is also true that the performance of Orthanc in the +presence of large databases has continuously improved over time, +especially when it comes to the speed of :ref:`DICOM C-FIND +`. Here is a generic setup that should provide best performance in the presence of large databases: @@ -29,7 +36,8 @@ * Make sure that :ref:`run-time debug assertions ` are turned off. A warning will show in the logs if this is not the - case. + case. Note that all pre-built binaries provided by Osimis are + correctly configured in that respect. * We suggest to use the default filesystem storage area. Of course, make sure that the filesystem is properly backup, and that diff -r 0fa1cf88c635 -r 60c91045bf2a Sphinx/source/faq/troubleshooting.rst --- a/Sphinx/source/faq/troubleshooting.rst Thu Jan 31 18:55:58 2019 +0100 +++ b/Sphinx/source/faq/troubleshooting.rst Thu Jan 31 19:13:52 2019 +0100 @@ -76,6 +76,10 @@ As a rule of thumb, the performance of the default SQLite engine built in Orthanc should run fine up to about 50,000 DICOM instances. + However, we have seen Orthanc running fairly well with more than 2 + millions of instances. This limit really depends upon your + application, and upon the patterns of access to the database. + Also check out the section about the :ref:`scalability`.