Hardware Requirements
From WikiDocs
The MOG pipeline uses a combination of 3 separate servers. How we utilize the 3 separate servers is explained below. We have provided basic hardware recommendations for your convenience.
Contents |
Overview:
MOG uses an SQL server, a FileServer, and a MOG server to manage, process and deliver all of the assets a team uses. By default all of these servers are installed onto one machine. Depending on the size of your team you may want to put the FileServer and the SQL server onto separate machines, although this is not necessary.
MOG Server:
The MOG server does not require much because it only manages TCP/IP connections. It does nothing more than pass MOG commands around to the various MOG components. It can be run on any machine and is completely portable.
Requirements:
- CPU: Any reasonable speed
- RAM: 1 GB
- Hard Drive: Any size
- Network: 1 gb
File Server:
We use the FileServer to host the repository where assets are stored. Team members will interact with this server in the same way they would interact with any file server. Traditionally, we have found this server's speeds to be limited more than hard drive speed than anything else. Most companies simply create a system volume on whatever fileserver they already have.
Requirements:
- RAM: 1 GB
- Hard Drive: striped raid, size varies depending on needs
- Network: Dual 1 gb
SQL Server:
The SQL server only stores the project’s metadata while the assets are stored on the FileServer. This helps keep the databases small and extremely fast. Team members will interact with this server through the MOG Client and other associated MOG components. This server tends to need a faster CPU because the number of database queries will increase proportionately to the team size.
Requirements:
- CPU: Faster the better
- RAM: 2 GB
- Hard Drive: 3 Drives
- System Drive: Minimal (20 GB)
- Data Drive: Minimal (20 GB)
- Log Drive: Minimal (20 GB)
- Network: 1 gb
Summary:
In a nutshell, we recommend a basic box for the MOG Server, a good file server capable of supporting the team, and a beefy CPU for the SQL Server. You need not put each server on it's own machine for smaller teams, but doing so can improve performance. Also improving the performance of a FileServer or SQLServer is a known and well defined process that can be custom tailored to the specific needs of each team. Basically, the scalability of the MOG pipeline is directly proportionate to the quality of the FileServer and SQL Server.
If you want faster update times, focus more on your FileServer. If you want punchy/fast interaction within the MOG Client, focus on the SQL Server.
