hawq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Pearce <Michael.Pea...@ig.com>
Subject HAWQ Perfomance.
Date Mon, 17 Oct 2016 21:11:46 GMT
Hi All,

As now HAWQ is being caught up with by some competitors in terms of real use performance,
and in some cases be out performed, most notably Spark 2.0 some queries we can perform faster
since project tungsten.

Obviously HAWQ still has the SQL completeness advantage but this also is a slowly changing
space, where Spark and others are improving.

Is there any plans to start looking improving the execution performance of HAWQ further with
parquet vectorisation and whole stage codegen?



On the note of the postgres 10 roadmap. Is there any plans of updating compatibility / the
fork of postgres to later versions (back merging), afaik HAWQ is a fork of 8.x which is quite

Im sure already all of these questions are answered/discussed, but it be great to get some
visibility into the roadmap for these areas for HAWQ.



The information contained in this email is strictly confidential and for the use of the addressee
only, unless otherwise indicated. If you are not the intended recipient, please do not read,
copy, use or disclose to others this message or any attachment. Please also notify the sender
by replying to this email or by telephone (+44(020 7896 0011) and then delete the email and
any copies of it. Opinions, conclusion (etc) that do not relate to the official business of
this company shall be understood as neither given nor endorsed by it. IG is a trading name
of IG Markets Limited (a company registered in England and Wales, company number 04008957)
and IG Index Limited (a company registered in England and Wales, company number 01190902).
Registered address at Cannon Bridge House, 25 Dowgate Hill, London EC4R 2YA. Both IG Markets
Limited (register number 195355) and IG Index Limited (register number 114059) are authorised
and regulated by the Financial Conduct Authority.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message