Database Server Hardware Requirement

Hardware planning & sizing for sql server

This guide outlines minimum software and hardware requirements for deploying Mattermost. Requirements may vary based on utilization and observing performance of pilot projects is recommended prior to scale out.

Mattermost can also be configured with a redundant, highly available, highly scalable mode to support large organizations. The following is an example that can be scaled up or down in size:

For enterprise deployments of 10, 000-20, 000 registered users with moderate usage and a peak of 2, 000-4, 000 concurrent users, the following hardware deployment configurations are recommended:

Proxy Server

One server with 4-8 vCPUs/cores, 16-32 GB RAM, minimum 4 GB SSD storage (Optional) Add one additional identical server for high availability mode, where one Mattermost server can be disabled or upgraded without interrupting service quality. Second server should be sized to carry the full load of the first server so performance does not degrade when the first server is taken offline.

Mattermost Server (1 to 2 depending on level of redundancy and high availability required)

One server with 4-8 vCPUs/cores, 16-32 GB RAM, minimum 4 GB SSD storage (Optional) Add one additional identical server for high availability mode, where one Mattermost server can be disabled or upgraded without interrupting service quality. Second server should be sized to carry the full load of the first server so performance does not degrade when the first server is taken offline. Note: The high availability option is available only by contacting the Enterprise Edition team.

Network Attached Storage

One NAS server with 4-8 TB of storage (based on moderate storage of 10 MB per user per month times 20, 000 users times 3 years of history, times 2x safety factor) or sized appropriately for your desired usage requirements. For high availability it is recommended you select a NAS server offering redundancy.

Database Server (2 recommended for redundancy)

One database server with 8-16 vCPUs/cores, 16-32 GB memory, minimum 100 GB SSD storage (Recommended) Add one identical database server to setup a Master-Slave configuration where the master can failover to slave with minimal disruption to service.

Notes:

Regular hard drives can be used in place of solid-state hard drives if having top performance is not a priority. If using a mix of HDD and SSD drives, the greatest performance gain would come from using SSD in the database server.

As an alternative to recommended storage sizing above, you can forecast your own storage usuage. Begin with a Mattermost server approximately 600 MB to 800 MB in size including operating system and database, then add the multiplied product of:

Estimated storage per user per month (see below), multipled by 12 months in a year Estimated mean average number of users in a year A 1-2x safety factor

Estimated storage per user per month

File usage per user varies significantly across industries. The below benchmarks are recommended:

Low usage teams (1-5 MB/user/month) Primarily use text-messages and links to communicate. Examples would include software development teams that heavily use web-based document creation and management tools, and therefore rarely upload files to the server. Medium usage teams (5-25 MB/user/month) Use a mix of text-messages as well as shared documents and images to communicate. Examples might include business teams that may commonly drag and drop screenshots, PDFs and Microsoft Office documents into Mattermost for sharing and review.
Advances in Software Engineering: International Conference, ASEA 2010, Held as Part of the Future Generation Information Technology Conference, FGIT ... in Computer and Information Science)
Book (Springer)
  • Used Book in Good Condition
hp HP 2.5-Inch 1200 GB Hot-Swap SCSI 2 MB Cache Internal Hard Drive 718162-B21
Personal Computer (hp)
  • State of the art design for maximum reliability and performance
  • Mission critical, high I/O environments: large database, e-mail/ messaging, ERP, and CRM
  • Ultimate reliability appropriate for intensive I/O

Related posts: