[Haskell-cafe] Storing big datasets

Mikhail Volkhov volhovm.cs at gmail.com
Sat May 7 10:58:25 UTC 2016


First, about external database engines -- I don't really understand how
should I store my own set datatype (let's say it's a red-black tree with
some extra information in nodes, something like that) in the key-value
db. No idea.

And yes, what about Redis, it's not supposed to work with sizes more
than RAM can hold.

Currently it's not the problem to switch application db. I'll check your
solutions (sqlite/HDBC/postgre/H2). Thanks!

On 05/07/2016 12:17 PM, Joachim Durchholz wrote:
> Am 07.05.2016 um 02:27 schrieb Lana Black:
>> Hi Mikhail,
>>
>> Have you considered external database engines? I suppose you could
>> benefit from using Redis in your case.
> 
> Wikipedia says that while Redis can use the disk as "virtual memory",
> that feature is deprecated, so it definitely expects to keep the whole
> dataset in memory. Which kind of defeats the whole point for Mikhail.
> 
> sqlite comes to mind. HDBC claims to have a driver for it, and it's
> linked into the application so there would be no additional setup required.
> 
> If Mikhail already has another database in his application, the setup
> cost is already paid for, and he might want to check whether that's fast
> enough for his purposes.
> I'd expect postgresql or mysql to be too slow, but H2 to work just fine.
> Of course that's just expectations, so testing would be needed.
> 
> Regards,
> Jo
> _______________________________________________
> Haskell-Cafe mailing list
> Haskell-Cafe at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe

-- 
Volkhov Mikhail
M3#38 ITMO study group 17'
Computer Technologies Department


More information about the Haskell-Cafe mailing list