Documentation toggle

Minimal Server Side Requirements

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

Minimal hardware requirements:

Concurrent ConnectionsCPU cores*RAM**HDD***Network Bandwidth****
1 connection2 cores3 GB20 GB4 MBit/s
2 connections2 cores3 GB30 GB6 MBit/s
5 connections2 cores6 GB50 GB10 MBit/s
10 connections3 cores8 GB100 GB15 MBit/s
20 connections4 cores12 GB200 GB30 MBit/s
30 connections6 cores16 GB300 GB50 MBit/s
60 connections8 cores20 GB600 GB100 MBit/s
60+ connections+1 core per 20 connections+1 GB per 5 connections+100 GB per 10 connections100+ MBit/s

*Equivalent of 5th generation Intel i5 2GHz CPU core (Q1’15 or later). For Virtual Machines: each virtual CPU appears as a single CPU core to the guest operating system. We recommend no more than one virtual CPU per physical core, or if hyperthreading supported, no more than two virtual CPUs per physical core.

**Additional RAM memory must be reserved for OS, Database, PACS and/or other services if installed in the same machine.

***HDD used for software (fixed 1 GB size) and temporary data cache (see cache management description). HDD performance (used for caching) directly affects image open speed (SDD, RAM or HI speed disk storage recommended).

****Network bandwidth will directly affect image open speed.

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 work load or specific data types.

Supported operating systems

MedDream supports the following operating systems:

  • Windows Server 2008 (64 bit) and newer;
  • Windows 10 (64 bit) and newer;
  • Linux (64 bit): Debian, Ubuntu, CentOS*, Fedora*.

*Advanced MPR/MIP feature is supported by Debian and Ubuntu only.

Supported Java runtime

Currently supported java runtime is Java 8 LTS. We recommend builds from AdoptOpenJDK.

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.