Bug 450751

Summary: TCP_NODELAY
Product: Red Hat Enterprise MRG Reporter: Rafael H. Schloming <rafaels>
Component: Release_NotesAssignee: Lana Brindley <lbrindle>
Status: CLOSED CURRENTRELEASE QA Contact: Kim van der Riet <kim.vdriet>
Severity: low Docs Contact:
Priority: low    
Version: betaCC: mhideo, tross
Target Milestone: ---Keywords: Documentation
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 1.0 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-06-11 07:56:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Rafael H. Schloming 2008-06-10 20:04:54 UTC 
In certain scenarios using TCP_NODELAY can significantly improve the performance
of the Java client. The use of TCP_NODELAY can be enabled by setting the
amqj.tcpNoDelay system property to true:

java -Damqj.tcpNoDelay=true ...

Scenarios where this may help include clients that do synchronous publish, as
well as clients that use many small transactions.
Comment 1 Lana Brindley 2008-06-11 07:56:57 UTC 
https://engineering.redhat.com/docbot/en-US/Red_Hat_Enterprise_MRG/1.0/html/MRG_Release_Notes/sect-MRG_Release_Notes-Known_Issues-RHM_Known_Issues.html

Also, a slight restructure of the known issues chapter.

LKB