ArangoDB 3.12 Product Release Announcement! Read the blog for details. Read Blog

Vector-5

Disk space usage with different journal sizes

Estimated reading time: 7 minutes

A while ago we wrote some blog article that explained how ArangoDB uses disk space. That article compared the disk usage of ArangoDB, CouchDB, and MongoDB for loading some particular datasets. In this post, we’ll show in more detail the disk usage of ArangoDB for insert, update, and delete operations. We’ll also compare it to CouchDB for reference.

(more…)

Dynamic script execution performance in ArangoDB

Estimated reading time: 7 minutes

In the previous post we published some performance results for ArangoDB’s HTTP and networking layer in comparison to that of some popular web servers. We did that benchmark to assess the general performance (and overhead) of the network and HTTP layer in ArangoDB.

Using ArangoDB as an application server

While HTTP is a good and (relatively) portable mechanism of shipping data between clients and servers, it is only a transport protocol. People will likely be using ArangoDB not only because it supports HTTP, but primarily because it is a database and an application server.In this post, we’ll..

(more…)

Infographic – comparing the disk space usage of MongoDB, CouchDB and ArangoDB

Estimated reading time: 0 minutes

As a follow-up of Jan’s blog post we have extracted some central figures and created this infographic for your reference.

(more…)

Disk space usage in ArangoDB

Estimated reading time: 8 minutes

In this post we’ll explain how ArangoDB stores collection data on disk and look at its storage space requirements, compared to other popular NoSQL databases such as CouchDB and MongoDB.

How ArangoDB allocates disk space

ArangoDB stores documents in collections. The collection data is persisted on disk so it does not get lost in case of a server restart.

(more…)

Benchmarking ArangoDB’s networking and HTTP layer

Estimated reading time: 7 minutes

…or: The Great Server Shootout

ArangoDB is a database server that talks HTTP with its clients: clients send HTTP requests to ArangoDB over TCP/IP, ArangoDB will process them and send back the results to the client, packaged as HTTP over TCP/IP.

ArangoDB’s communication layer is thus the foundation for almost all database operations, and it needs to be fast to not become a bottleneck, blocking further database operations.To assess the actual performance of the communication layer, we did some benchmarks that compare ArangoDB’s network and HTTP processing capabilities with those of other..

(more…)

Preliminary Performance Tests for mruby and V8

Estimated reading time: 3 minutes

Note: We changed the name of the database in May 2012. AvocadoDB is now called ArangoDB

I’m still investigating the possibility to use mruby as embedded language for AvocadoDB, see me last post. I managed to create an interactive shell to play with mruby. Now am trying to do some performance tests. Note that mruby is still “alpha”, so DO NOT take these test to seriously. They are basically just for me to learn, how to use mruby.

Exposing a C function to MRUBY

The first function I need is a timing function. I’ve implemented such a function in C using gettimeofday. Now in order to make it..

(more…)

Under a microscope: how ArangoDB stores data in RAM and data is secured consistently nonetheless in case of a server crash

Estimated reading time: 4 minutes

Note: We changed the name of the database in May 2012. AvocadoDB is now called ArangoDB.

AvocadoDB uses AppendOnly memory-mapped files with frequent fsync. Derived data (indices, etc.) is stored in the main memory only. This article explains why that particular combination leads to high performance and consistent data at the same time―even in case of a system failure.

Classical database systems – a bulk of data and insufficient main memory

Put simply, there are three possible settings regarding databases:

  • Setting 1: All data fits into the main memory.
  • Setting 2: The complete data pool does..
(more…)
« 1 ...
3 4 5 6 7
»