WIP - Add some MM instances listings examples#574
Conversation
|
|
||
| For a typical <MainPlatformName /> enterprise level deployment for a small team (<20 users), we provide a shortlist of Azure, AWS and GCP capable instances. | ||
|
|
||
| * [Azure](https://cloudprice.net/?_numberOfCores_min=4&_numberOfCores_max=6&_memoryInMB_min=6&_memoryInMB_max=8&timeoption=month) |
There was a problem hiding this comment.
rather than links that can be invalid in few months I suggest to write down the spec that is required and write it could be for example azure / aws - ec2 or gpc machine.
…setups' of github.com:MerginMaps/docs into 555-document-custom-server-hw-requirements-for-various-setups
|
|
||
| We recommend using a dedicated host machine with 8 GB of memory. The requirements for CPU and persistent storage depend largely on the frequency of project updates and the anticipated size of the data you expect to store respectively. | ||
|
|
||
| For a typical <MainPlatformName /> enterprise level deployment for a small team (<20 users), the following specs are sufficient: |
There was a problem hiding this comment.
see line 10 - shouldn't it be in line with the table?
There was a problem hiding this comment.
@varmar05 I need some help here trying to figure out some specs for different teams sizes on MM. Without any metrics is difficult to make some assumptions. Should we add some metrics/monitoring to our cloud instance?
| subfolders | ||
| subproject | ||
| subprojects | ||
| synchronization |
There was a problem hiding this comment.
we use UK spelling, so in this case, synchronisation (synchronization is US spelling :) ) This should be removed from the wordlist.
|
|
||
| For large teams and/or HA, please contact our <MerginMapsEmail id="sales" desc="sales team" />. | ||
|
|
||
| The requirements for CPU and persistent storage depend largely on the frequency of project updates and the anticipated size of the data you expect to store respectively. |
There was a problem hiding this comment.
| The requirements for CPU and persistent storage depend largely on the frequency of project updates and the anticipated size of the data you expect to store respectively. | |
| The requirements for CPU and persistent storage depend largely on the frequency of project updates and the anticipated size of stored data. |
tomasMizera
changed the title
|
This is already on recent documentation with some generic setup. There is no need of different tiers setups. |
3 participants
Refers to #555