Server requirements (virtual appliance)
The table below summarizes the system requirements for the (virtualized) TrendMiner server. TrendMiner always recommends provisioning the recommended specifications to ensure a consistent and performant UX.
Resource | Minimum | Minimum with MLHub[a] | Recommended | ||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
vCPU | 16 | + 1 core per 4 active kernels (per user) + 1 core per 8 notebook tiles (per user per dashboard) | 16 | ||||||||||||||||||||||||||||||||||||||||||||||
RAM | 64GB | + 1GB per active kernel (per user) + 256MB per notebook tile (per user per dashboard) | 96GB | ||||||||||||||||||||||||||||||||||||||||||||||
Disk | SSD, 500GB, 250MB/s | SSD, 500GB, 250MB/s | SSD, 500GB, 250MB/s | ||||||||||||||||||||||||||||||||||||||||||||||
[a] Contact your Customer Success Manager for more information on MLHub Notebook and Machine Learning Model capabilities | |||||||||||||||||||||||||||||||||||||||||||||||||
These resources may be increased with increasing TrendMiner usage or number of connected data sources. Please work with TrendMiner support to determine the projected resource requirements.
Additional memory requirements
On top of the above requirements TrendMiner requires the memory to be scaled along with the CPUs at a ratio of at least 1-2 and preferably 1-4. In practice this would result in 128GB RAM for a server with 32 CPUs and 256GB RAM for a server with 64 CPUs.
Additional disk requirements
For virtual appliance installations the first disk will only recognize 200GB of disk space. Please make sure to set up your virtual appliance with a 200GB disk and use the extend disk functionality in TrendMiner to further extend the disk after initial installation.All disk space >200GB in the initial installation will be permanently lost!
The required disk space highly depends on the usage of the system: number of users and the amount of items they save on the system + the number of tags which are added and indexed. If usage increases further disk space increases might be required.
TrendMiner strongly advises thick provision of the VM TrendMiner is running on to avoid over-provisioning and increase write performance. Over-provisioning can result in TrendMiner going down because of a full disk without upfront alarm to the TrendMiner admin.
Hypervisor requirements
The TrendMiner Virtual Appliance is imported into a virtualization environment. TrendMiner provides images for VMware ESXi and Microsoft Hyper-V.
TrendMiner supports these hypervisors:
VMware ESXi 7.0 or higher.
Microsoft Windows Hyper-V Server 2012 R2 or higher
Network requirements
Gigabit Ethernet or better is required for TrendMiner to work.
The TrendMiner appliance uses Kubernetes (K3S) as its infrastructure layer, which needs a range of IP addresses for internal communication between different pods and services. The following IP addresses should not be used by other applications/servers running on the network on which TrendMiner is deployed:
Outgoing Network configuration
To be able to comply to the license audit terms, you need to allow communication to our collector system by opening communications on a firewall or proxy server.
option 1 (preferred):
from: TrendMiner Appliance Server (Linux)
to: license.trendminer.cloud (DNS based IP whitelisting)
port: TCP 443
option 2:
from: TrendMiner Appliance Server (Linux)
to: 13.248.161.236 and 3.33.158.180
port: TCP 443
In case you cannot open or allow access to the internet on specific port and IP, you will need to provide us the metrics manually, as described in this document Disabling Automated Data Collection & Manual Data Export Requirement.