|
From: Daniel H. <da...@de...> - 2016-04-24 16:47:13
|
First I run 30 queries and I got a timeout around query 20. With the option -XX:+UseG1GC I have solved issue. Then I increment the number of queries to 300. Now I got the first timeout around query 100. So the problem continues. The issue is not with queries. Queries are not complex. Most of them end in one second. Also, I shuffle them in each experiment. The behavior is always the same, there is an instant after that all queries get timeout. Now I'm reading the GC documentation and testing with different parameters. Cheers, Daniel El 24/04/16 a las 13:14, Bryan Thompson escribió: > Great. However, if this was GC overhead, then there is likely a > remaining issue with the queries or the configuration. I would not > expect normal queries to incur that kind of GC overhead. > > Thanks, > Bryan > > On Sun, Apr 24, 2016 at 12:12 PM, Daniel Hernández <da...@de... > <mailto:da...@de...>> wrote: > > I solved the problem of timeouts. The issue was generated by the > garbage > collector. I used the option -XX:+UseG1GC that is documented here: > > http://www.oracle.com/technetwork/java/javase/tech/vmoptions-jsp-140102.html#G1Options > > > Thanks to all! > Daniel > > > ------------------------------------------------------------------------------ > Find and fix application performance issues faster with > Applications Manager > Applications Manager provides deep performance insights into > multiple tiers of > your business applications. It resolves application problems > quickly and > reduces your MTTR. Get your free trial! > https://ad.doubleclick.net/ddm/clk/302982198;130105516;z > _______________________________________________ > Bigdata-developers mailing list > Big...@li... > <mailto:Big...@li...> > https://lists.sourceforge.net/lists/listinfo/bigdata-developers > > |