| Summary: | [dstore] Need an option to set TCP NODELAYACKS | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Tools] Target Management | Reporter: | Missing name <olivier.gauneau> | ||||||||
| Component: | RSE | Assignee: | David McKnight <dmcknigh> | ||||||||
| Status: | RESOLVED FIXED | QA Contact: | Martin Oberhuber <mober.at+eclipse> | ||||||||
| Severity: | major | ||||||||||
| Priority: | P3 | CC: | xuanchen | ||||||||
| Version: | 3.2.1 | Flags: | xuanchen:
review+
|
||||||||
| Target Milestone: | 3.3 RC3 | ||||||||||
| Hardware: | Other | ||||||||||
| OS: | other | ||||||||||
| Whiteboard: | |||||||||||
| Bug Depends on: | |||||||||||
| Bug Blocks: | 347445 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Missing name
A test with NODELAY shows great improvement on performance Is this request specific to dstore? Does it affect the client only, or server only, or both? Problem is on both sides client and server and I assume it is specific to dstore. I have worked on this issue with David McKnight who will add more information. Created attachment 196749 [details]
patch to provide TCPNODELAY option
Xuan, could you please review this? The fix looks good. Thanks. Thanks for the review, Xuan. I've committed the change to cvs. Created attachment 196872 [details]
patch fixing the build on J2SE-1.4
This checkin broke the build, because dstore.core must still be J2SE-1.4 compliant and Boolean.parseBoolean() is not in J2SE-1.4
I fixed the issue by converting to
Boolean.valueOf(s).booleanValue().
Please also apply this fix to the 3.2.2+ Stream, which is currently also broken.
And, please ensure that a J2SE-1.4 JVM is registered in your Workspace (Preferences : Java : JVM's) in order to detect such issues in your workspace.
I released the change for 3.3RC3. Shouldn't we document system properties like the new DSTORE_TCP_NO_DELAY somewhere ? Created attachment 196888 [details]
patch with option described in constants file
Other properties like this have been defined in a constants file and described there as this patch does.
I released the update for 3.3rc3, but cannot build currently due to bug 347744 . |