5 ms·
I'm interested, can anyone give a quick overview of why you'd use this over Elasticsearch?
by catmanjan 8y ago
I'm interested, can anyone give a quick overview of why you'd use this over Elasticsearch?
- francislavoie 8y agoWell for one, Java is ridiculously memory hungry. The resource costs of Elasticsearch is the #1 reason I'm not using it. I've seen a few projects which had the aim of reimplementing the Elasticsearch backend in Rust, but were incomplete. That would be my ideal solution, personally.
- bheesham 8y agoI don't know how true that is anymore, that "Java is ridiculously memory hungry". It does power billions of devices, after all. :-P
- gshack 8y agoSo does the diesel engine, but's not eco friendly.
- ousta 8y agowhy do you think they called their product "elastic"? java heap size? 32gb? above that and you are in for problems
- nithril 8y agowhich problem? There is no problem, especially since the latest gc. Only tradeof
- ousta 8y agothis is a limitation. For instance if you have billions of docs you need 200 tiny servers and have to deal with the communication/administration/monitoring between all of those. anything around 32gb and you will have perf drops everytime the GC works too hard..
- nithril 8y agoNot true since g1gc
- neeleshs 8y agoOpenJ9 is a low memory footprint jvm
- realusername 8y agoYes, exactly the same for me, I've tried all the configuration possible with the jvm (that I know of) but nothing really worked to make it use a more reasonable amount of memory.