# HG changeset patch # User Sebastien Jodogne # Date 1548957358 -3600 # Node ID 0fa1cf88c635398f48ffd22fb67bbcfab31c99a3 # Parent a846a8f6d9a69c1e252a2776caf89b5b4b9bc276 typo diff -r a846a8f6d9a6 -r 0fa1cf88c635 Sphinx/source/faq/scalability.rst --- a/Sphinx/source/faq/scalability.rst Thu Jan 31 18:41:44 2019 +0100 +++ b/Sphinx/source/faq/scalability.rst Thu Jan 31 18:55:58 2019 +0100 @@ -20,10 +20,6 @@ Here is a generic setup that should provide best performance in the presence of large databases: -* Make sure that :ref:`run-time debug assertions ` - are turned off. A warning will show in the logs if this is not the - case. - * Make sure to use the latest release of Orthanc (1.5.3 at the time of writing). @@ -31,6 +27,10 @@ ` to store the database index (3.0 at the time of writing). Make sure that ``EnableIndex`` is set to ``true``. +* Make sure that :ref:`run-time debug assertions ` + are turned off. A warning will show in the logs if this is not the + case. + * We suggest to use the default filesystem storage area. Of course, make sure that the filesystem is properly backup, and that technologies such as RAID are enabled. Make sure that the option @@ -55,6 +55,5 @@ mode, especially at the startup of Orthanc. The logs may contain very important information regarding performance. -* Make sure to read guides about the :ref:`tuning of PostgreSQL +* Make sure to read guides about the `tuning of PostgreSQL `__. -