Database load testing is a crucial aspect when performing different tests on adatabase. Load testing itself creates a great image of how a database performsunder load, in terms of resilience but also performance. In this study, we set upthree different databases: MySQL, MongoDB, and HCL Notes Database. In order for the database load testing tool to better perform actions on the database,we set up a REST API. This REST API implemented all the necessary functions to Create, Read, Update and Remove (CRUD) data. In the experiment,a notification was used as data. The load testing tool was used to create testplans that performed all the CRUD for one notification by sending out the requests, and then to perform multiple plans of requests at the same time to loadtest the database. Response time was collected from all the requests sent out.The results gathered from this showed a clear winner, this being MySQL withthe lowest overall response time and also never showed a sign of crashing. HCLNotes Database performed the slowest and almost managed to run all the testsfully, whilst MongoDB performed better than HCL Notes Database but didn’tmanage to fully run as many tests as the other two databases. Concluding this,MySQL in this test, performed the best and in a similar scenario as the one setup, is the most suitable database.
| Identifer | oai:union.ndltd.org:UPSALLA1/oai:DiVA.org:liu-195846 |
| Date | January 2023 |
| Creators | Hallengren, William |
| Publisher | Linköpings universitet, Institutionen för datavetenskap |
| Source Sets | DiVA Archive at Upsalla University |
| Language | English |
| Detected Language | English |
| Type | Student thesis, info:eu-repo/semantics/bachelorThesis, text |
| Format | application/pdf |
| Rights | info:eu-repo/semantics/openAccess |
Page generated in 0.0014 seconds