Curoverse Public Beta Program » History » Version 3
Tom Clegg, 07/21/2015 07:32 PM
| 1 | 1 | Radhika Chippada | h1. Scalability |
|---|---|---|---|
| 2 | |||
| 3 | 3 | Tom Clegg | This page lists some size limits imposed by the Curoverse public beta cluster. |
| 4 | 1 | Radhika Chippada | |
| 5 | 2 | Bryan Cosca | Note: These are not limitations of Arvados; they're limitations of the specific cluster configuration. |
| 6 | |||
| 7 | 1 | Radhika Chippada | h3. Maximum API Server Request Size |
| 8 | |||
| 9 | The maximum request size supported by the arvados API server in Curoverse public beta is 128MiB. |
||
| 10 | |||
| 11 | Thus this limits the size of the request that can be sent by a client when making an API request. For example, the manifest text used to create a new collection cannot exceed this limit. |
||
| 12 | |||
| 13 | h3. Compute Nodes |
||
| 14 | |||
| 15 | Each compute node in Curoverse public beta cluster uses the configuration of 16 cores, 60GiB RAM, with 300GiB of scratch space on disk to run jobs. |
||
| 16 | |||
| 17 | The maximum number of simultaneous compute nodes is 256. |
||
| 18 | |||
| 19 | h3. Docker |
||
| 20 | |||
| 21 | Docker is not available on the standard shell node in Curoverse public beta. |
||
| 22 | |||
| 23 | Users who would like to use a shell node to build Docker images can contact Curoverse support at support@curoverse.com and explain what they plan to work on. |