Hi David, Please check this thread to see if you need to stay with Postgres or switch to Ignite: https://stackoverflow.com/questions/55208376/apache-ignite-vs-sql-server-performance/55230967#55230967
In general, it's expected that Ignite is to be used for relational DBs acceleration - when those can't process large data sets and an upgrade to expensive hardware is not the way to go. So, with Ignite the volume of data is usually measured in hundreds of GBs and more and the scalability is one of the keys to benefit. - Denis On Wed, Jun 5, 2019 at 3:37 AM David <[email protected]> wrote: > Hi Ilya, > > thx for helping me > > the column is collocated. Still I need around ~10+Servers to match one PG > Server speed for a group by. > > What do you mean with use "collocated=true"? > I thought it is only needed in case you dont have collocated data and still > want to have full result set. > and its not needed when data are collocated. Do I understand it wrong? > > > btw side question: > when using sqlline.sh with the "distributedJoins=true" > all queries are x-times slower than without > > which makes totaly sense in case for non collocated data. > But it is also the case for collocated data, which makes no sense. > > sqlline.sh --verbose=true -u > jdbc:ignite:thin://127.0.0.1/?distributedJoins=true > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
