This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
system_requirements [2022/05/04 11:53] antreas |
system_requirements [2022/05/04 12:08] antreas |
||
---|---|---|---|
Line 45: | Line 45: | ||
Additionally, slides can be stored either on local disks attached to the VM or in Azure Blob Storage. | Additionally, slides can be stored either on local disks attached to the VM or in Azure Blob Storage. | ||
When possible, it is recommended to prefer [[https://docs.microsoft.com/en-us/azure/storage/blobs/data-lake-storage-introduction|Azure Data Lake Storage Gen2]] over plain Azure Blob Storage, as this type of service performs directory management operations, such as moving and renaming slides and directories, a lot faster. | When possible, it is recommended to prefer [[https://docs.microsoft.com/en-us/azure/storage/blobs/data-lake-storage-introduction|Azure Data Lake Storage Gen2]] over plain Azure Blob Storage, as this type of service performs directory management operations, such as moving and renaming slides and directories, a lot faster. | ||
+ | === PMA.core cache requirements === | ||
+ | Regardless of the choice or combination of the storage media used, the system requires some space on | ||
+ | a local or network disk where cache data will be stored and accessed. PMA.core allows you to define | ||
+ | the cache retention policy and informs you about it's size. As a general rule of thumb, the cache | ||
+ | capacity should be around 10% of the total size of the available whole slide images. | ||
==== Client Side ===== | ==== Client Side ===== | ||