Documentation toggle

Minimal Server-Side Requirements

Minimal server-side requirements of MedDream DICOM Viewer are as below:

Minimal hardware requirements:

Concurrent ConnectionsCPU cores*RAM**
1 connection4 cores8 GB
2 connections4 cores8 GB
5 connections4 cores8 GB
10 connections4 cores12 GB
20 connections6 cores16 GB
30 connections8 cores32 GB
60 connections16 cores32 GB
60+ connections+1 core per 10 connections+1 GB per 5 connections

* Equivalent of 5th generation Intel i5 2GHz CPU core (Q1’15 or later).
** Additional RAM must be reserved for OS, Database, PACS and/or other services if installed in the same machine.
The storage is used for software (fixed 1 GB size) and temporary data cache. Performance of the caching storage directly affects image open speed, therefore SSD, RAM or high-speed disk storage is recommended for it.

NOTE: It is recommended to allocate the fastest disk storage, with free space for 10 days worth of new studies, for the MedDream cache in order to have a better viewing performance.

The network bandwidth will directly affect image open speed. At least 100 Mbit/s is recommended.

NOTE: Minimal hardware requirements depend on number of concurrent users, workload and image types. It is recommended to allocate 20-80% more resources for unusual workload or specific data types.

Supported operating systems

Recommended operating systems on server side:

  • Windows Server 2019, Windows Server 2022;
  • Windows 10, Windows 11 (64-bit only) and above;
  • Linux: Debian 12, Ubuntu 20.04 LTS, CentOS 7.9-2009, Fedora 37. The minimum glibc version is 2.15 for x86_64 and 2.27 for aarch64.

Supported Java runtime

Currently supported supported Java runtime is Java 17 LTS. We recommend builds from The build must be 64-bit, as under 32-bit builds some kinds of DICOM images will not be displayed.

Decommissioning of MedDream

A particular version of MedDream is supported for a limited time (see the Info window or User Manual). When support is no longer provided, we strongly recommend to update to a supported version. Be aware that the customer is responsible for outcome (including, but not limited to, personal data protection) from operating a not supported version. Not supported software versions are used at customer’s own risk.