As a general rule, when you encounter an issue, always make sure that you use the most recent version of Orthanc.
Also make a search on the Orthanc Users discussion group, and make a search in the present Orthanc Book (there is a search field at the top of this page). Your issue might indeed have already been discussed in the past or in the FAQ.
RemoteAccessAllowedoption in the configuration file to
true. It is then strongly advised to set
trueand to add a user to the
RegisteredUsersoption, also in the configuration file.
Run-time debug assertions: If performance is important to you,
make sure to add the option
cmake while compiling Orthanc. Indeed, by default, run-time debug assertions
are enabled, which can seriously impact performance, especially if
your Orthanc server stores a lot of DICOM instances.
Note that the official Docker images of Orthanc <= 1.0.0
were not compiled in
Release mode. As a consequence, to improve
performance, make sure to use either the mainline version of the
docker pull jodogne/orthanc to ensure you use the
most recent version of the mainline), or versions more recent than
Orthanc slows down if storing many files: The default database engine that is built in Orthanc is SQLite. As SQLite is above all a lightweight database engine, it is not designed to store very large datasets. If you are sure that you have properly disabled run-time debug assertions (cf. above), but still experience degradation in performance over time, you should seriously consider switching to a more scalable database engine. To this end, you can notably check out the official PostgreSQL plugin.
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.
Orthanc Explorer is slow under Windows on the localhost:
localhostwhen specifying the network address of a server. Users have reported that this minor change can massively improve performance on Windows. Starting with Orthanc 1.0.1, the samples from the source distribution have been adapted in this way.
If you experience slow DICOM transfers under GNU/Linux, please
read the following bug report. This
issue does not affect all the versions of GNU/Linux. A patch to
this issue is shipped with the Orthanc source code. In order to take
advantage of this patch, you need to statically link Orthanc against
DCMTK by using the
-DUSE_SYSTEM_DCMTK=OFF flag when invoking