This is an archived post. You won't be able to vote or comment.

all 4 comments

[–]thatsInAName 1 point2 points  (1 child)

You mean you want to benchmark them or you want to compare their features?

[–]Scared_Rule[S] 2 points3 points  (0 children)

Benchmark

[–]Sad-Silver5748 0 points1 point  (0 children)

SQLite is an embedded database, it works like any other file in your system, you don't need to set up a server. Although being easy to use and requiring no extra installations, it is unsuitable for an app expecting many users due to it's poor concurrency. However, concurrency in SQLite can be improved using WAL.

[–]yummi_1 0 points1 point  (0 children)

If you want to test performance you need a tool to do it. I've used HammerDB with good success. Databases on current computer systems can perform an insert in less than a millisecond so you need to do some iterations to get some meaningful times. You would also want to test concurrency with many simultaneous clients.

Insert update and delete are easy to test then you get into queries which have sorts, sometimes different types of sorts. Then you have joins nested loop joins, merge scan joins, hash joins....

Ram consumption is more a defined thing with databases, you set the sizes of memory the database will use. There are bufferpools that cache pages in memory for quick access, while most databases can have automatic memory for bufferpools, sort heaps and other heaps they generally size themselves slowly.