<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/4.6.6">
</HEAD>
<BODY>
Hi,<BR>
<BR>
While investigating some CI failures in query (timeouts), I've narrowed down the issue to the Jgroups protocol stack being used. <BR>
Running a 'mvn clean install' in the query/ module takes about 6min (when timeout does not happen). If I run instead: <BR>
<BR>
mvn -Dtest.protocol.jgroups=udp clean install<BR>
<BR>
Time goes down to around 50s. Recent changes in core's jgoups-tcp.xml for the tests were the removal of the loopback=true and the modification of the bundler_type, but they don't seem to affect the outcome.<BR>
<BR>
FYI, taking a single test and stripping down from it everything but the cluster formation and data population (5 objects) leads to the cpu hotspot below, and it takes almost 1 minute <BR>
<BR>
I'd be happy to change the query tests to udp, but first would like to hear your thoughts about this issue<BR>
<BR>
Gustavo<BR>
<BR>
<PRE>
+----------------------------------------------------------------------------------+------------------+--------------------+
| Name | Time (ms) | Invocation Count |
+----------------------------------------------------------------------------------+------------------+--------------------+
| +---java.net.SocketInputStream.read(byte[], int, int, int) | 101,742 100 % | 4,564 |
| | | | |
| +---java.net.SocketInputStream.read(byte[], int, int) | | |
| | | | |
| +---java.io.BufferedInputStream.fill() | | |
| | | | |
| +---java.io.BufferedInputStream.read() | | |
| | | | |
| +---java.io.DataInputStream.readInt() | | |
| | | | |
| +---org.jgroups.blocks.TCPConnectionMap$TCPConnection$Receiver.run() | | |
| | | | |
| +---java.lang.Thread.run() | | |
+----------------------------------------------------------------------------------+------------------+--------------------+
</PRE>
</BODY>
</HTML>