[CAMEL-4686] Messages larger than 64KB can be processed very slowly due to file read buffer of 1 byte

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.6.0
• Fix Version/s: 2.7.5, 2.8.3, 2.9.0
• Component/s: camel-core

Environment

ServiceMix 4.3, Solaris 10

• Patch Info: Patch Available
• Estimated Complexity: Novice
• Assignee: Claus Ibsen
• Reporter: metatech
• Created: 16/Nov/11 11:03
• Updated: 16/Nov/11 12:34
• Resolved: 16/Nov/11 12:31

Description

When the message body is larger than 64KB, the message is stored on the disk by CachedOutputStream and read back later by FileInputStreamCache.
A thread dump during a load test shows that the execution is most of the time waiting in the "InputStream.read()" method calls.
The "truss" output shows that the file is read back 1 byte at a time, which makes the calls very slow.

A first workaround (setting property "CamelCachedOutputStreamThreshold" to 10000000 on the CamelContext's properties) helped in some case.

The cause is that the FileInputStreamCache does not use a BufferInputStream to read on the disk, although the
CachedOutputStream does properly use a BufferOutputStream.
See
http://java.sun.com/docs/books/performance/1st_edition/html/JPIOPerformance.fm.html#17675

A trivial patch is attached, which provides a fix.

Reference :
http://servicemix.396122.n5.nabble.com/DefaultTraceFormatter-is-very-slow-for-messages-gt-64KB-td4902840.html
This problem was first noticed when the trace was enabled on the CamelContext, but it occurs also in other scenarios.

Issue Links

• relates to: CAMEL-4687 Wrap FileInputStream in BufferedInputStream in the Converter classes to ensure loading from file is faster