![]() We also observed that the ArangoDB application needed more restarts than the MySQL application. It is good as a DB for mission-critical applications and suitable for dealing with core/financial data.ĪrangoDB is a good choice for applications that need frequent fetching of bulk details and write-heavy applications. Though Arango DB seems to be faster than MySQL in various tests conducted, MySQL has an edge over reliability, stability, and ease of data export & import. Success response of MySQL DB improved on using the flat structure. ArangoDB can provide an edge in the case of Write heavy Applications and Bulk Reads where the size of data per document/record is high as compared to MySQL.ĪrangoDB is better in terms of success response within the given time of 120 seconds. While conducting this exercise, it was observed that ArangoDB performed way better than MySQL DB in terms of write operations. This is derived after studying the results of Fetch/Find one. While conducting this exercise, we found that the Response time for read queries is the same for both ArangoDB and MySQL databases (even taking latency into account). The recorded data is as follows:ĬPU and Memory Utilization for ArangoDB and MySQL Tests were conducted with 4 Cores, 8 GB RAM, 8 GB Disk configuration.Īfter executing the above test cases, the results were recorded in terms of Latency (ms), DB and Application CPU and Memory Utilization(%), Success Rate.ArangoDB and MySQL used a flat table structure.Tests were conducted with 2 Cores, 4 GB RAM, 4 GB Disk configuration.Order Details table joined with Pizza Table whereas ArangoDB stored data in a nested structure. Tests for the following scenarios were carried out for both ArangoDB and MySQL: Arrival rate distribution is mentioned in the Data Table under the “Machine wise Arrival rate column. To load the test, we used 3 boxes, 2 Azure VMs, and a Laptop.We used artillery to load test our applications and had set a timeout of 120 seconds for each scenario to be tested.Spring boot applications were configured to fetch Top 50 orders of a given City.Each Record or document was of size 10KB.Both Arango and MySQL were loaded with 50000+ Records/documents.We used 2 VMs from Talentica Network TestBox1, TestBox2 and my Laptop was used as TestBox3– Used to execute Artillery Test.For Test 2, we spawned 2 VMs in Azure each having 4 Cores, 8 GB RAM, 8 GB Disk.VM3 & VM4– Used to execute Artillery Test.VM 2 - Hosted our Pizza Delivery Spring boot application with 2048 memory and pool size 20. ![]() VM1 - Hosted ArangoDB and MySQL over Docker.For Test 1, we spawned 4 VMs in Azure each having 2 Cores, 4 GB RAM, 4 GB Disk.We used the following configurations to carry out the performance test. Arango vs MySQL: Performance Benchmarking MySQL Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software. It delivers a very fast, multi-threaded, multi-user, and robust SQL (Structured Query Language) database server. MySQL is an open-source relational database management system (RDBMS). It can be scaled horizontally or vertically. High-performance applications can be built using a convenient SQL-like query language or JavaScript extensions. So, here we go! Overview of ArangoDBĪrangoDB is a multi-model, distributed, open-source database with flexible data models for documents, graphs, and key-values. This triggered us to carry out a comparison between MySQL and Arango DB. Recently, we got into a project where our client was interested in implementing the application with a multi-model Database called Arango DB that could be easily built in any relational database.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |