Fork me on GitHub
#datahike
<
2022-01-01
>
dgr00:01:14

qq about Datalevin’s and Datahike’s memory needs. I’ve got a simple side-project that I’m looking at. It will probably run on a VPS with minimal memory (2 GB, perhaps 4 GB). How are both Datalevin and Datahike with memory pressure? I don’t have a lot of data (few hundred entities, each with maybe 50 attributes), but I want to make sure the DB doesn’t suck all memory in the system. Anyway, not sure if anybody has done any tests but general rules of thumb would be interesting to help make the decision. I’m going to crosspost this to #datalevin.

timo18:01:07

Hi @U7BEY9U10. One obvious question for Datahike: Which backend do you want to use? Datahike supports a couple of different options here, like memory, file, jdbc and others.

dgr18:01:26

Ah, good question. I should have specified. I think the file backend is what I want.

timo18:01:26

I guess it should be working without problem with a file-backend if that suits you.

timo18:01:15

@UQVCR784A is working on a RocksDB-backend. That should be suitable as well

timo18:01:22

but it's not done yet