2 out of 5 with 1 ratings

Xeround Reviews

XeRound review

about Xeround · · Helpful Not helpful Report as spam

On paper XeRound looks like a real marvel, like the cure to all evils. There is only one detail from our experience with then but it is a big one for us, it partitions every table, that's a good thing you'd think, but it even partitioned our 4 rows table, when we did a SELECT * from table_with_4_rows it took 4 seconds to fetch the 4 rows. We asked them if there was some configuration or anything to fix on our end, their reply was that "select alls are very expensive and our query was not optimized".

So word of advise: take the free package if you can and see if it works for you.



I work at Xeround and would like to share the following with you:

Xeround partitions tables in order to achieve HA and scalability, we are aware that this might - in some rare cases like "select all" reduce query performance. To that end we are investing quite a lot of effort to minimize the degradation that our users might encounter for specific use cases.

In fact performance is high on our radar and in our upcoming releases we are introducing several performance enhancements.

In terms of general best practices when working with SQL databases, there are a quite a few things that users should always pay attention to:

  1. Be sure that you’re using indexes and avoid full-table scans.
  2. If you’re noticing a query takes longer than you would have expected, use EXPLAIN statement to make sure there are no full-table scans and do create indexes as needed.
  3. BTREE and HASH indexing: the default type of indexing is BTREE. However, equality operations with high cardinality are served faster with HASH indexing.
  4. It is better to use “ORDER BY” by columns that are BTREE indexed.

Yuval Lubowich