Mercurial > hg > orthanc-book
comparison Sphinx/source/faq/troubleshooting.rst @ 358:011b01ccf52d
fixing external hyperlinks
author | Sebastien Jodogne <s.jodogne@gmail.com> |
---|---|
date | Mon, 30 Mar 2020 18:47:35 +0200 |
parents | 99ba212989cc |
children | d217af5e6cb3 |
comparison
equal
deleted
inserted
replaced
357:6b432ce3a56e | 358:011b01ccf52d |
---|---|
3 Troubleshooting | 3 Troubleshooting |
4 =============== | 4 =============== |
5 | 5 |
6 As a general rule, when you encounter an issue, always make sure that | 6 As a general rule, when you encounter an issue, always make sure that |
7 you use the `most recent version | 7 you use the `most recent version |
8 <http://www.orthanc-server.com/download.php>`__ of Orthanc. | 8 <https://www.orthanc-server.com/download.php>`__ of Orthanc. |
9 | 9 |
10 Also make a search on the `Orthanc Users discussion group | 10 Also make a search on the `Orthanc Users discussion group |
11 <https://groups.google.com/forum/#!forum/orthanc-users>`__, and make a | 11 <https://groups.google.com/forum/#!forum/orthanc-users>`__, and make a |
12 search in the present Orthanc Book (there is a search field at the top | 12 search in the present Orthanc Book (there is a search field at the top |
13 of this page). Your issue might indeed have already been discussed in | 13 of this page). Your issue might indeed have already been discussed in |
63 most recent version of the mainline), or versions more recent than | 63 most recent version of the mainline), or versions more recent than |
64 ``jodogne/orthanc:1.1.0``. | 64 ``jodogne/orthanc:1.1.0``. |
65 | 65 |
66 * **Orthanc slows down if storing many files**: The default database | 66 * **Orthanc slows down if storing many files**: The default database |
67 engine that is built in Orthanc is `SQLite | 67 engine that is built in Orthanc is `SQLite |
68 <https://www.sqlite.org/>`__. As SQLite is above all a lightweight | 68 <https://www.sqlite.org/index.html>`__. As SQLite is above all a |
69 database engine, it is not designed to `store very large datasets | 69 lightweight database engine, it is not designed to `store very large |
70 <https://www.sqlite.org/whentouse.html>`__. If you are sure that you | 70 datasets <https://www.sqlite.org/whentouse.html>`__. If you are sure |
71 have properly disabled run-time debug assertions (cf. above), but | 71 that you have properly disabled run-time debug assertions |
72 still experience degradation in performance over time, you should | 72 (cf. above), but still experience degradation in performance over |
73 seriously consider switching to a more scalable database engine. To | 73 time, you should seriously consider switching to a more scalable |
74 this end, you can notably check out the :ref:`official PostgreSQL | 74 database engine. To this end, you can notably check out the |
75 plugin <postgresql>`. | 75 :ref:`official PostgreSQL plugin <postgresql>`. |
76 | 76 |
77 As a rule of thumb, the performance of the default SQLite engine | 77 As a rule of thumb, the performance of the default SQLite engine |
78 built in Orthanc should run fine up to about 50,000 DICOM instances. | 78 built in Orthanc should run fine up to about 50,000 DICOM instances. |
79 However, we have seen Orthanc running fairly well with more than 2 | 79 However, we have seen Orthanc running fairly well with more than 2 |
80 millions of instances. This limit really depends upon your | 80 millions of instances. This limit really depends upon your |
92 on Windows. Starting with Orthanc 1.0.1, the samples from the | 92 on Windows. Starting with Orthanc 1.0.1, the samples from the |
93 source distribution have been adapted in this way. | 93 source distribution have been adapted in this way. |
94 | 94 |
95 - As an alternative, you can disable IPv6 support. This is a | 95 - As an alternative, you can disable IPv6 support. This is a |
96 Windows-specific problem that is discussed `here | 96 Windows-specific problem that is discussed `here |
97 <http://superuser.com/questions/43823/google-chrome-is-slow-to-localhost>`__ | 97 <https://superuser.com/questions/43823/google-chrome-is-slow-to-localhost>`__ |
98 and `here | 98 and `here |
99 <http://stackoverflow.com/questions/1726585/firefox-and-chrome-slow-on-localhost-known-fix-doesnt-work-on-windows-7>`__. | 99 <https://stackoverflow.com/questions/1726585/firefox-and-chrome-slow-on-localhost-known-fix-doesnt-work-on-windows-7>`__. |
100 | 100 |
101 * If you experience **slow DICOM transfers under GNU/Linux**, please | 101 * If you experience **slow DICOM transfers under GNU/Linux**, please |
102 read the `following bug report | 102 read the `following bug report |
103 <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785400>`__. This | 103 <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785400>`__. This |
104 issue does *not* affect all the versions of GNU/Linux. A patch to | 104 issue does *not* affect all the versions of GNU/Linux. A patch to |
134 name such as ``C:\Orthanc``. | 134 name such as ``C:\Orthanc``. |
135 | 135 |
136 * If **Orthanc crashes when handling one large DICOM file**, this most | 136 * If **Orthanc crashes when handling one large DICOM file**, this most |
137 probably indicates a memory allocation error. Indeed, the `official | 137 probably indicates a memory allocation error. Indeed, the `official |
138 Windows binaries | 138 Windows binaries |
139 <http://www.orthanc-server.com/download-windows.php>`__ are compiled | 139 <https://www.orthanc-server.com/download-windows.php>`__ are compiled |
140 using a 32bit compiler. As a consequence, Orthanc only has access to | 140 using a 32bit compiler. As a consequence, Orthanc only has access to |
141 less than 4GB of RAM. If this is an important limitation for you, | 141 less than 4GB of RAM. If this is an important limitation for you, |
142 precompiled command-line versions of Orthanc for Windows 64bit are | 142 precompiled command-line versions of Orthanc for Windows 64bit are |
143 available courtesy of `Osimis | 143 available courtesy of `Osimis |
144 <http://www.osimis.io/en/download.html>`__. | 144 <https://www.osimis.io/en/download.html>`__. |