News for hackers. Stuff that matters.
Re:PostgreSQL vs. Impala by lazyjones on Tuesday March 11, 2014 @10:05AM (#7379237)
I'd like to see the code / data so I can try to reproduce these results. If it took them 6 hours to load 25m rows / 10GB with PostgreSQL, they must have screwed it up (deliberately?).
Re:PostgreSQL vs. Impala by milliams on Tuesday March 11, 2014 @09:56AM (#7379187)
A graph with no units on the y-axis (and not even stated clearly in the text) put me completely off reading this article.
Re:PostgreSQL vs. Impala by dagilmore on Wednesday March 12, 2014 @10:53PM (#7389825)
I thought it was safe to assume that seconds were the unit of choice, but next time i'll be more clear. Thanks for the suggestion
Re:PostgreSQL vs. Impala by ecolak on Tuesday March 11, 2014 @01:06PM (#7380590)
Impala, imitating Google's Dremel, is specifically designed for OLAP scenarios with its columnar storage structure and the compression algorithms that go along with it. This is not a fair comparison. Try doing OLTP with Impala and you'll see what I mean.
Re:PostgreSQL vs. Impala by dagilmore on Wednesday March 12, 2014 @10:52PM (#7389819)
Great point! I mentioned it in the post, did you read it?

"Note that the properties of a relational database are well suited to online-transaction processing (OLTP). Such a system guarantees consistency and availability, and it supports extreme multi-tenancy. However, complex logic over large amounts of data does not perform well"

Re:PostgreSQL vs. Impala by copergi on Tuesday March 11, 2014 @11:34AM (#7379836)
Benchmarks where we're not given the data, code, scripts, etc to reproduce them are not useful.
Re:PostgreSQL vs. Impala by dagilmore on Wednesday March 12, 2014 @10:58PM (#7389839)
If you look in the citations, you'll see everything you need to reproduce the results!