There is also a nice blog post on disk space usage, here. If the journal size is big, less files are needed, ergo less file descriptors (and their associated resources) are needed. My Environment ArangoDB Version: 3.4.3 Storage Engine: RocksDB Deployment Mode: Cluster Deployment Strategy: ArangoDB Starter Configuration: Infrastructure: own Operating System: CentOS 7 Total RAM in your machine: 32Gb Disks in use: HDD. Later to avoid legal issues, the name was changed to ArangoDB in May 2012. ArangoDB first version was released in spring 2012. Memory: each Database / Collection will take up space on the disk (and also in memory when loaded.)įor a collection, the number of file descriptors needed at any time is dependent of the journal size defined for it. ArangoDB tries to combine their use cases together to build an 'all-in-one' database so that users do not need to use a second database for different types of data. Some of those resources, for each Database / Collection, are:įiles on disk: space and file descriptors needed. If no value is provided for -server.database it will default to system, meaning the subsequent invocations of arangorestore will each overwrite. This can be achieved by providing the -server.database option in the same way as it can be done for arangodump. The only thing you have to keep in mind, are the resources that are needed for databases and their collections. arangorestore needs to be told to which database to restore the data to. For a detailed list of changes to the ArangoDB core programs and tools, please refer to the version specific changelogs: Changelogs 3. As far as I know, there are virtually no limits to the number of databases in ArangoDB.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |