[JBoss JIRA] (JGRP-2504) Poor throughput over high latency TCP connection when recv_buf_size is configured
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-2504?page=com.atlassian.jira.plugin... ]
Bela Ban commented on JGRP-2504:
--------------------------------
I'll reply in detail later, but I know what the problem is: I thought I was using {{TCP.recv_buf_size}} (which *is* set correctly), but instead I used {{TCP.TcpServer.recv_buf_size}} which is set *after* {{bind()}}. I'll fix this today.
> Poor throughput over high latency TCP connection when recv_buf_size is configured
> ---------------------------------------------------------------------------------
>
> Key: JGRP-2504
> URL: https://issues.redhat.com/browse/JGRP-2504
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 5.0.0.Final
> Reporter: Andrew Skalski
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 5.1
>
> Attachments: SpeedTest.java, bla5.java, bla6.java, bla7.java, delay-ip.sh
>
>
> I recently finished troubleshooting a unidirectional throughput bottleneck involving a JGroups application (Infinispan) communicating over a high-latency (~45 milliseconds) TCP connection.
> The root cause was JGroups improperly configuring the receive/send buffers on the listening socket. According to the tcp(7) man page:
> {code:java}
> On individual connections, the socket buffer size must be set prior to
> the listen(2) or connect(2) calls in order to have it take effect.
> {code}
> However, JGroups does not set the buffer size on the listening side until after accept().
> The result is poor throughput when sending data from client (connecting side) to server (listening side.) Because the issue is a too-small TCP receive window, throughput is ultimately latency-bound.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (DROOLS-5684) DMN DT Analysis Misleading rule definition refinements
by Matteo Mortari (Jira)
[ https://issues.redhat.com/browse/DROOLS-5684?page=com.atlassian.jira.plug... ]
Matteo Mortari updated DROOLS-5684:
-----------------------------------
Description:
The original definition is:
bq. P tables can be “misleading” when rule contains hyphen input entry (“irrelevant”) and output is not lowest priority
as in the following example:
!screenshot-2.png|thumbnail!
which was implemented with [DROOLS-3785].
( ref: https://youtu.be/eQRDc6fq2yw?t=1293 )
Further refinements checked to avoid duplicating "Misleading rule" reports when in fact the rules were already reported as "Masked", with: [DROOLS-5368]
However, a table such as the below would inadvertently still report misleading rules:
!screenshot-1.png|thumbnail!
So the new definition is refined to:
{quote}P tables can be “misleading” when:
* rule contains hyphen input entry (“irrelevant”)
* and output is not lowest priority
* the hyphen in the misleading rule, correspond to a value (not an hyphen) in the mislead('d) rule
{quote}
was:
The original definition is:
bq. P tables can be “misleading” when rule contains hyphen input entry (“irrelevant”) and output is not lowest priority
as in the following example:
!screenshot-2.png|thumbnail!
which was implemented with [DROOLS-3785].
Further refinements checked to avoid duplicating "Misleading rule" reports when in fact the rules were already reported as "Masked", with: [DROOLS-5368]
However, a table such as the below would inadvertently still report misleading rules:
!screenshot-1.png|thumbnail!
So the new definition is refined to:
{quote}P tables can be “misleading” when:
* rule contains hyphen input entry (“irrelevant”)
* and output is not lowest priority
* the hyphen in the misleading rule, correspond to a value (not an hyphen) in the mislead('d) rule
{quote}
> DMN DT Analysis Misleading rule definition refinements
> ------------------------------------------------------
>
> Key: DROOLS-5684
> URL: https://issues.redhat.com/browse/DROOLS-5684
> Project: Drools
> Issue Type: Bug
> Components: dmn engine
> Reporter: Matteo Mortari
> Assignee: Matteo Mortari
> Priority: Major
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> The original definition is:
> bq. P tables can be “misleading” when rule contains hyphen input entry (“irrelevant”) and output is not lowest priority
> as in the following example:
> !screenshot-2.png|thumbnail!
> which was implemented with [DROOLS-3785].
> ( ref: https://youtu.be/eQRDc6fq2yw?t=1293 )
> Further refinements checked to avoid duplicating "Misleading rule" reports when in fact the rules were already reported as "Masked", with: [DROOLS-5368]
> However, a table such as the below would inadvertently still report misleading rules:
> !screenshot-1.png|thumbnail!
> So the new definition is refined to:
> {quote}P tables can be “misleading” when:
> * rule contains hyphen input entry (“irrelevant”)
> * and output is not lowest priority
> * the hyphen in the misleading rule, correspond to a value (not an hyphen) in the mislead('d) rule
> {quote}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (DROOLS-5684) DMN DT Analysis Misleading rule definition refinements
by Matteo Mortari (Jira)
[ https://issues.redhat.com/browse/DROOLS-5684?page=com.atlassian.jira.plug... ]
Matteo Mortari updated DROOLS-5684:
-----------------------------------
Attachment: screenshot-2.png
> DMN DT Analysis Misleading rule definition refinements
> ------------------------------------------------------
>
> Key: DROOLS-5684
> URL: https://issues.redhat.com/browse/DROOLS-5684
> Project: Drools
> Issue Type: Bug
> Components: dmn engine
> Reporter: Matteo Mortari
> Assignee: Matteo Mortari
> Priority: Major
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> The original definition is:
> bq. P tables can be “misleading” when rule contains hyphen input entry (“irrelevant”) and output is not lowest priority
> which was implemented with [DROOLS-3785].
> Further refinements checked to avoid duplicating "Misleading rule" reports when in fact the rules were already reported as "Masked", with: [DROOLS-5368]
> However, a table such as the below would inadvertently still report misleading rules:
> !screenshot-1.png|thumbnail!
> So the new definition is refined to:
> {quote}P tables can be “misleading” when:
> * rule contains hyphen input entry (“irrelevant”)
> * and output is not lowest priority
> * the hyphen in the misleading rule, correspond to a value (not an hyphen) in the mislead('d) rule
> {quote}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (DROOLS-5684) DMN DT Analysis Misleading rule definition refinements
by Matteo Mortari (Jira)
[ https://issues.redhat.com/browse/DROOLS-5684?page=com.atlassian.jira.plug... ]
Matteo Mortari updated DROOLS-5684:
-----------------------------------
Description:
The original definition is:
bq. P tables can be “misleading” when rule contains hyphen input entry (“irrelevant”) and output is not lowest priority
as in the following example:
!screenshot-2.png|thumbnail!
which was implemented with [DROOLS-3785].
Further refinements checked to avoid duplicating "Misleading rule" reports when in fact the rules were already reported as "Masked", with: [DROOLS-5368]
However, a table such as the below would inadvertently still report misleading rules:
!screenshot-1.png|thumbnail!
So the new definition is refined to:
{quote}P tables can be “misleading” when:
* rule contains hyphen input entry (“irrelevant”)
* and output is not lowest priority
* the hyphen in the misleading rule, correspond to a value (not an hyphen) in the mislead('d) rule
{quote}
was:
The original definition is:
bq. P tables can be “misleading” when rule contains hyphen input entry (“irrelevant”) and output is not lowest priority
which was implemented with [DROOLS-3785].
Further refinements checked to avoid duplicating "Misleading rule" reports when in fact the rules were already reported as "Masked", with: [DROOLS-5368]
However, a table such as the below would inadvertently still report misleading rules:
!screenshot-1.png|thumbnail!
So the new definition is refined to:
{quote}P tables can be “misleading” when:
* rule contains hyphen input entry (“irrelevant”)
* and output is not lowest priority
* the hyphen in the misleading rule, correspond to a value (not an hyphen) in the mislead('d) rule
{quote}
> DMN DT Analysis Misleading rule definition refinements
> ------------------------------------------------------
>
> Key: DROOLS-5684
> URL: https://issues.redhat.com/browse/DROOLS-5684
> Project: Drools
> Issue Type: Bug
> Components: dmn engine
> Reporter: Matteo Mortari
> Assignee: Matteo Mortari
> Priority: Major
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> The original definition is:
> bq. P tables can be “misleading” when rule contains hyphen input entry (“irrelevant”) and output is not lowest priority
> as in the following example:
> !screenshot-2.png|thumbnail!
> which was implemented with [DROOLS-3785].
> Further refinements checked to avoid duplicating "Misleading rule" reports when in fact the rules were already reported as "Masked", with: [DROOLS-5368]
> However, a table such as the below would inadvertently still report misleading rules:
> !screenshot-1.png|thumbnail!
> So the new definition is refined to:
> {quote}P tables can be “misleading” when:
> * rule contains hyphen input entry (“irrelevant”)
> * and output is not lowest priority
> * the hyphen in the misleading rule, correspond to a value (not an hyphen) in the mislead('d) rule
> {quote}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (DROOLS-5684) DMN DT Analysis Misleading rule definition refinements
by Matteo Mortari (Jira)
[ https://issues.redhat.com/browse/DROOLS-5684?page=com.atlassian.jira.plug... ]
Matteo Mortari updated DROOLS-5684:
-----------------------------------
Description:
The original definition is:
bq. P tables can be “misleading” when rule contains hyphen input entry (“irrelevant”) and output is not lowest priority
which was implemented with [DROOLS-3785].
Further refinements checked to avoid duplicating "Misleading rule" reports when in fact the rules were already reported as "Masked", with: [DROOLS-5368]
However, a table such as the below would inadvertently still report misleading rules:
!screenshot-1.png|thumbnail!
So the new definition is refined to:
{quote}P tables can be “misleading” when:
* rule contains hyphen input entry (“irrelevant”)
* and output is not lowest priority
* the hyphen in the misleading rule, correspond to a value (not an hyphen) in the mislead('d) rule
{quote}
was:
The original definition is:
bq. P tables can be “misleading” when rule contains hyphen input entry (“irrelevant”) and output is not lowest priority
which was implemented with [DROOLS-3785].
Further refinements checked to avoid duplicating "Misleading rule" reports when in fact the rules were already reported as "Masked", with: [DROOLS-5368]
However, a table such as the below would inadvertently still report misleading rules:
!screenshot-1.png!
So the new definition is refined to:
{quote}P tables can be “misleading” when:
* rule contains hyphen input entry (“irrelevant”)
* and output is not lowest priority
* the hyphen in the misleading rule, correspond to a value (not an hyphen) in the mislead('d) rule
{quote}
> DMN DT Analysis Misleading rule definition refinements
> ------------------------------------------------------
>
> Key: DROOLS-5684
> URL: https://issues.redhat.com/browse/DROOLS-5684
> Project: Drools
> Issue Type: Bug
> Components: dmn engine
> Reporter: Matteo Mortari
> Assignee: Matteo Mortari
> Priority: Major
> Attachments: screenshot-1.png
>
>
> The original definition is:
> bq. P tables can be “misleading” when rule contains hyphen input entry (“irrelevant”) and output is not lowest priority
> which was implemented with [DROOLS-3785].
> Further refinements checked to avoid duplicating "Misleading rule" reports when in fact the rules were already reported as "Masked", with: [DROOLS-5368]
> However, a table such as the below would inadvertently still report misleading rules:
> !screenshot-1.png|thumbnail!
> So the new definition is refined to:
> {quote}P tables can be “misleading” when:
> * rule contains hyphen input entry (“irrelevant”)
> * and output is not lowest priority
> * the hyphen in the misleading rule, correspond to a value (not an hyphen) in the mislead('d) rule
> {quote}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (DROOLS-5684) DMN DT Analysis Misleading rule definition refinements
by Matteo Mortari (Jira)
[ https://issues.redhat.com/browse/DROOLS-5684?page=com.atlassian.jira.plug... ]
Matteo Mortari updated DROOLS-5684:
-----------------------------------
Description:
The original definition is:
bq. P tables can be “misleading” when rule contains hyphen input entry (“irrelevant”) and output is not lowest priority
which was implemented with [DROOLS-3785].
Further refinements checked to avoid duplicating "Misleading rule" reports when in fact the rules were already reported as "Masked", with: [DROOLS-5368]
However, a table such as the below would inadvertently still report misleading rules:
!screenshot-1.png!
So the new definition is refined to:
{quote}P tables can be “misleading” when:
* rule contains hyphen input entry (“irrelevant”)
* and output is not lowest priority
* the hyphen in the misleading rule, correspond to a value (not an hyphen) in the mislead('d) rule
{quote}
was:
The original definition is:
bq. P tables can be “misleading” when rule contains hyphen input entry (“irrelevant”) and output is not lowest priority
which was implemented with [https://issues.redhat.com/browse/DROOLS-3785]
> DMN DT Analysis Misleading rule definition refinements
> ------------------------------------------------------
>
> Key: DROOLS-5684
> URL: https://issues.redhat.com/browse/DROOLS-5684
> Project: Drools
> Issue Type: Bug
> Components: dmn engine
> Reporter: Matteo Mortari
> Assignee: Matteo Mortari
> Priority: Major
> Attachments: screenshot-1.png
>
>
> The original definition is:
> bq. P tables can be “misleading” when rule contains hyphen input entry (“irrelevant”) and output is not lowest priority
> which was implemented with [DROOLS-3785].
> Further refinements checked to avoid duplicating "Misleading rule" reports when in fact the rules were already reported as "Masked", with: [DROOLS-5368]
> However, a table such as the below would inadvertently still report misleading rules:
> !screenshot-1.png!
> So the new definition is refined to:
> {quote}P tables can be “misleading” when:
> * rule contains hyphen input entry (“irrelevant”)
> * and output is not lowest priority
> * the hyphen in the misleading rule, correspond to a value (not an hyphen) in the mislead('d) rule
> {quote}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months