We've used it for years as well, and (for us) the absolutely worst fact about it is that it is a memory hog like crazy. Even without any accesses at all, it nee

We've used it for years as well, and (for us) the absolutely worst fact about it is that it is a memory hog like crazy. Even without any accesses at all, it needs like 32 GB RAM on our nodes, for a 0.5 TB DB (with a bunch of indexes). I guess this is by design and is a compromise that requires this, but it makes it very expensive to deploy on AWS, where RAM is the real differentiator for this (actually storing the table on EBS is super cheap compared to the RAM required...). It's also very difficult to analyse to see where the RAM is going, this is one thing at least that could be improved. I would not use it for any newer projects unless this was fixed.