Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created on 01-11-2017 08:20 PM - edited 09-16-2022 03:54 AM
I got a table of size ~1gb and I tried to setup hdfs caching as described in this 'Using HDFS caching with Impala" doc, with replication factor of 2
Created 01-12-2017 03:40 PM
What kind of performance difference are we talking about? 5%? 100%?
It's helpful to look at execution summaries or profiles to drill down on where the difference is (if you're using impala-shell, you can get them with the summary; and profile; commands after running a query).
If the whole data set you're querying fits in memory, HDFS caching may not be that beneficial, since the OS buffer cache can be pretty effective at keeping the data in memory, especially if you're re-running the same query on the same data back-to-back. Also if the query is somewhat complex, it can get CPU-bound pretty quickly.
Created 01-12-2017 03:40 PM
What kind of performance difference are we talking about? 5%? 100%?
It's helpful to look at execution summaries or profiles to drill down on where the difference is (if you're using impala-shell, you can get them with the summary; and profile; commands after running a query).
If the whole data set you're querying fits in memory, HDFS caching may not be that beneficial, since the OS buffer cache can be pretty effective at keeping the data in memory, especially if you're re-running the same query on the same data back-to-back. Also if the query is somewhat complex, it can get CPU-bound pretty quickly.
Created 01-12-2017 04:24 PM
Given the size of the dataset, I believe the data fits in memory and its not providing any additional performance improvement.
Thanks!