Based on info in [1], using -Djava.net.preferIPv4Stack=true should speed things up if issues are indeed related to IPV6. Maryanne, Julian, can you try running Pig tests with the -Djava.net.preferIPv4Stack=true JVM param? If that helps, maybe we could just add that parameter to pom.xml.
Alternatively, if Pig tests are slow for some people, I can certainly break them out into unit and integration tests and only have integration tests actually execute Pig. This seems like a less desirable option IMHO, as integration tests are not run on 'mvn install.' Thanks, Eli [1] https://developer.ibm.com/answers/questions/284205/how- can-we-improve-performance-in-javanetinet6addr.html On Mon, Mar 13, 2017 at 10:38 AM, Maryann Xue <[email protected]> wrote: > Here a Mac Pro with Comcast network connection (not much better than what > Julian has in a ski cabin maybe). Core build took 3:22 min, and Pig took > 07:38 min. > > On Mon, Mar 13, 2017 at 9:08 AM, Julian Hyde <[email protected]> wrote: > > > The env was a ski cabin. And as you know, ski cabins often have blunt > > knives, poor quality coffee machines, and routers that don't support > ipV6. > > The last of these might be a factor. > > > > Julian > > > > > > > > > On Mar 11, 2017, at 7:14 PM, Eli Levine <[email protected]> wrote: > > > > > > Not seeing this on my Linux or Mac machines. What env are you seeing > > this in? > > > > > > Thanks, > > > > > > Eli > > > > > >> On Mar 11, 2017, at 8:14 AM, Julian Hyde <[email protected]> wrote: > > >> > > >> The Pig tests seem to be running very slowly (several minutes), and > CPU > > is idle. Is anyone else seeing this? > > >> > > >> A thread dump reveals a wait in java/net/Inet6AddressImpl. > lookupAllHostAddr. > > If so, maybe we’re hitting [1]. > > >> > > >> Julian > > >> > > >> [1] https://developer.ibm.com/answers/questions/284205/how- > > can-we-improve-performance-in-javanetinet6addr.html < > > https://developer.ibm.com/answers/questions/284205/how- > > can-we-improve-performance-in-javanetinet6addr.html> > > > > >
