If you plan to host RollMaster on your own server infrastructure, we recommend using server‑class hardware and components to ensure good performance and reliability. While the exact configuration will depend on your company’s size, user count, and transaction volume, the guidance below outlines general best practices.
Recommended server‑class components
Processor: A modern Intel Xeon‑class CPU — RollMaster operations like order entry and data updates benefit from multiple cores and high clock speeds.
Memory (RAM): 32 GB or more is recommended. More RAM improves performance, especially for environments with many concurrent users.
Storage: Use SSD drives configured in RAID 10 for fast disk access and data safety. SSDs significantly improve performance compared with traditional HDDs, especially for databases.
Redundancy & reliability:
Redundant power supplies help ensure uptime.
Maintain reliable backup systems for both system and database files.
Why these recommendations matter
RollMaster often handles database operations, reporting, and concurrent user activity, which benefit from server‑class hardware.
Faster CPUs and more RAM can improve responsiveness for users and reduce delays during high‑load operations such as batch posting or report generation.
RAID‑protected SSD storage helps protect data and improves performance, especially when handling multiple simultaneous read/write operations.
Working with IT support
These are high‑level guidelines — your local IT team or service provider should tailor the final specs based on:
How many users will access the system at once
How much data and transaction volume you handle
Whether the server will host additional services (e.g., SQL Server)
Virtualization strategy (physical vs. VM infrastructure)
A tailored sizing assessment by your IT support team ensures that your server configuration aligns with both performance needs and budget.
💡 Pro Tips
Virtualized environments: Many organizations run RollMaster servers inside virtual machines using technologies like VMware or Hyper‑V. In those cases, ensure the VM is provisioned with dedicated CPU and RAM resources — performance can be sensitive to overcommitment.
Backup and DR: In addition to redundant power and RAID storage, consider regular backups and a disaster‑recovery plan for your server environment.