Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
sizingguide [2019_02_13 11:24]
kamran changed and approved for newer appliances
sizingguide [2019_09_25 11:33] (current)
jim [For Production:]
Line 11: Line 11:
 ==== For Production: ==== ==== For Production: ====
  
-This will be dependent on the use case, number of users, and modules deployed but as a minimum:+We are often asked about recommended architecture when companies wish to try and design their Enterprise File Fabric architecture for production use for '​x'​ number of users. 
 + 
 +Let’s first try and define some terms that we can use to dig into this. 
 + 
 +‘**Concurrent users**’ is defined as the number of users actively using the system at the same time. These ‘Concurrent users’ will all have an active session and will be engaged in a range of activities on the system. ​ In addition, we define ‘**Throughput**’ as the requests per second that the system has to facilitate. 
 + 
 +When any number of users are logged in they are not all necessarily synchronously interacting with the File Fabric. At any particular point in time, some users may be searching for data,  others may be browsing file, others uploading or downloading a file, and perhaps some will stop for a minute to check email and not be actually interacting with the File Fabric at all. 
 + 
 +We could make the assertion, for example, that there are 1000 concurrent users, but they are not all making 1000 concurrent requests. The throughput that such concurrent users generate would only be based on their actual interactions at any given moment in time and even these interactions may be dealing with cached data layers that do not necessarily increase system throughput. 
 + 
 +This is often forgotten when people start thinking about the number of users they have to server or cater for. We are often asked to help prospect and customers to calculate that ‘x’number of users = '​y'​ Throughput.  
 + 
 +We can provide some guidance on requests like these, but only if we have detailed data sets as baselines. ​ Every deployment is different, and is heavily influenced by use cases and other factors such as network latency, storage under management: ie. each deployment has multiple variables that change the equation outside of just the number of users. 
 + 
 + 
 +As a minimum single machine configuration please consider the below but as outlined above this will be dependent on the use case, number of users, and modules deployed but as a minimum:
  
   * 8 GB RAM for the Virtual Machine   * 8 GB RAM for the Virtual Machine
Line 18: Line 33:
   * 40GB for DB Volume on SSD or performant storage   * 40GB for DB Volume on SSD or performant storage
   * Static IP, DNS registered FQDN, SSL certificate   * Static IP, DNS registered FQDN, SSL certificate
 +
 +Remember that the File Fabric is horizontally and vertically scalable, so if the initial design is thought out and executed well, scaling out in real-time based on demand can easily be achieved.
  
 Please [[https://​storagemadeeasy.com/​files/​ce370f2df47a3b29c9539d3575560496.pdf|download]] and review the comprehensive sizing document to assist in scoping out enterprise deployment sizing. Please [[https://​storagemadeeasy.com/​files/​ce370f2df47a3b29c9539d3575560496.pdf|download]] and review the comprehensive sizing document to assist in scoping out enterprise deployment sizing.