Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Not A Problem
-
1.1.0
-
None
-
None
Description
It seems that Hive on Spark has some room for performance improvement on job submission. Specifically, we are calling refreshLocalResources() for every job submission despite there is are no changes in the jar list. Since Hive on Spark is reusing the containers in the whole user session, we might be able to optimize that.
We do need to take into consideration the case of dynamic allocation, in which new executors might be added.
This task is some R&D in this area.