Understand this is pure ram db, but what if i use swap instead?

[sprappcom]

curious on performance for theoretical and practical suggestion on how i can also use this in limited ram instances.
pls answer with consideration to using the fastest nvme ssd with 1mil iops type e.g. samsung pro 990.

1. under what circumstances for "high db usage" scenario and ratio of ram to db size for swap use? what i mean is, if i have 10gb db, and only 4gb ram with swap size of 10gb, is this "advisable?" or maybe i have 10gb db but 8gb ram and 2gb swap. under what circumstances will this "work" as normal db and better than other db solutions? i dont really understand the mechanism below the layout so im curious on such use case.

2. if i put 80% of db as use in swap (practically using the high speed nvme drive) how long do u think the drive can last? and how much performance impact will it be?

3. is there a way i can limit ram use and offload the rest to swap? i have ramdisk / ramdrive to use.

[jcwangxp]

You can think CrossDB is more like Redis, it's RAM oriented DB, so if you have limited RAM, then the DB size should be less than 75% of the RAM size, otherwise, the performance will be very poor, and you'd better use traditional DB like Sqlite or nosql DB like Rocksdb. If you need client-server DB, you can try the H2, firebird or MySQL/PGSQL/MongoDB. There's no magic, if you need max speed, then you need big RAM.