comparison Sphinx/source/faq/scalability.rst @ 861:c3e169fe22da

delayed deletion
author Alain Mazy <am@osimis.io>
date Thu, 30 Jun 2022 17:59:23 +0200
parents 3e8a3a900e9e
children f72b2dd172da
comparison
equal deleted inserted replaced
860:3e8a3a900e9e 861:c3e169fe22da
385 might sound counter-intuitive). This is especially true with HDD 385 might sound counter-intuitive). This is especially true with HDD
386 drives, that can be much slower than SSD (`an user has reported 386 drives, that can be much slower than SSD (`an user has reported
387 <https://groups.google.com/g/orthanc-users/c/1lga0oFCHN4/m/jF1inrc4AgAJ>`__ 387 <https://groups.google.com/g/orthanc-users/c/1lga0oFCHN4/m/jF1inrc4AgAJ>`__
388 a 20 times speedup by switching from HDD to SSD). 388 a 20 times speedup by switching from HDD to SSD).
389 389
390 If switching from HDD to SDD is not applicable, it is possible to 390 If switching from HDD to SDD is not applicable, you may also use
391 create an :ref:`storage area plugin <creating-plugins>` that delays 391 the :ref:`Delayed Deletion plugin <delayed-deletion-plugin>` .
392 the actual deletion from the filesystem. The plugin would maintain a 392 The plugin would maintains a queue of files to be removed. The actual
393 queue (e.g. as a SQLite database) of files to be removed. The actual 393 deletion from the filesystem is done asynchronously in a
394 deletion from the filesystem would be done asynchronously in a
395 separate thread. 394 separate thread.
396
397 We are looking for funding from the industry to implement such a
398 plugin.