3 ms·
Hi tyingq, thank you for your comment. Your deduction goes a bit too far - yes, the technology demo in this post is in the same space as that case study, but n
by mgl 3y ago
Hi tyingq, thank you for your comment.
Your deduction goes a bit too far - yes, the technology demo in this post is in the same space as that case study, but no - the implementation is completely different.
Many firms replace their in-database processing with in-memory-like stores but it would be very difficult to achieve similarly low latency and still provide real-time updates with the solutions that you mentioned like Redis, ElasticSearch, etc. due to a number of the internal design features of these data stores.
The most fundamental issues are:
a) inefficient memory allocation model hurting CPU cache usage,
b) implementation model based on painful data serialization/deserialization transformations wasting both CPU and memory resources.
This is why we build and share this demo which enables you to achieve a 20x lower latency than other available options.
You may find a a bit more what's behind the demo in the Technology section here:
https://ultrafastsearchengine.com/#/details https://ultrafastsearchengine.com/#/details
- tyingq 3y ago> You may find a a bit more what's behind the demo... That only says "the engine is a Java-based proprietary solution which was about 20x faster than comparable implementations in Coherence, Ignite or Hazelcast. (Yes, we tested it.)". So, comparable to those. Some sort of Java friendly in-memory cache. Perhaps, for this specific kind of data (dates/location/room-type/price/availability), you've figured out an optimal storage/retrieval layout that's fast. That seems plausible. What doesn't seem plausible is that your cache is generally 20x faster than every other cache in the space.
- mgl 3y agoThe combination of storage/retrieval/calculation, executed close to the actual data, is what gives 20x advantage. CPU cache is hard-to-believe fast, see: https://stratoflow.com/latency-numbers-every-java-developer-should-know/ https://stratoflow.com/latency-numbers-every-java-developer-...