It takes a couple of hours to set up development the first time, mainly due to the dataload and an empty build. m4.4xl is what we use in pre-merge testing, and I think m5.4xl will work, too. I think you can stop the instance and pause per-hour charging except for the EBS volume, and then you won't have to do a data load when you re-start the instance. Additionally, your ccache should be more populated on the second recompile. I usually use ./buildall.sh -skiptests -ninja ...
On Thu, Apr 12, 2018 at 1:34 AM, Abhishek Sharma <[email protected]> wrote: > Hi All, > > I am trying to run "source ~/Impala/bin/bootstrap_development.sh" > on an r4.4x large AWS machine (16 core, 120 gb machine). > > But it is taking a lot of time. I am working on a patch for one of the JIRA > issues and this is really slowing me down. > > Does it take so much time to setup development environment for Impala or am > I > missing something. > > > -- > Nice Day > > Abhishek Sharma > Bachelor of Technology > IIT Kanpur (2009) >
