5 ms·
We heavily use elasticsearch as part of Kiln's infrastructure. We've actually found it to be an insanely useful tool: it scales extremely well, it's highly red
by gecko 14y ago
We heavily use elasticsearch as part of Kiln's infrastructure. We've actually found it to be an insanely useful tool: it scales extremely well, it's highly redundant, it's trivial to extend, and it is fast. We've managed to move every last bit of our search infrastructure (including source code), using over 100 million documents representing 182 GB of data, and we still get search times around 10 ms or less. It's so fast we've got an entirely new feature built around it coming out in the next few weeks. It's just that awesome.
The only downside we've hit with ES is poor documentation. In all other respects, if you need search, I can unconditionally recommend it.
- luser001 14y agoQuick, possibly beginner question: do you hold all the data in RAM, or is some of it on disk?
- gecko 14y agoWe store it entirely in RAM. ES stores data on disk for persistence, but prefers to keep its working set fully in RAM, and will (by design) crash by default if it runs out of memory.
- PascalW 14y agoI agree, ES is awesome. The poor documentation can be annoying indeed, but Shay Banon is always very helpful on the discussion groups so that's a big plus.
- te_chris 14y ago+1 on this, a better side bar or something on docs would be wonderful, but the tech just rules. The ease of setting up a redundant cluster is great, not to mention the just insane response speed. We switched a few page loads from mongodb to elastic search, mongo was taking ~13000 ms per page load, elastic took ~250 (2 mm records).
- Mpdreamz 14y agoAre you guys still using NEST?