[
https://issues.apache.org/jira/browse/THRIFT-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679242#action_12679242
]
Kevin Clark commented on THRIFT-357:
------------------------------------
{code}
/**
* Creates a new connection either by reusing an object off the stack or
* by allocating a new one entirely
@@ -483,7 +494,13 @@
* Returns a connection to the stack
*/
void TNonblockingServer::returnConnection(TConnection* connection) {
{code}
Is this just the diff giving us the wrong comment for that method?
> Buffer and Connection bloat in TNonBlockingServer
> -------------------------------------------------
>
> Key: THRIFT-357
> URL: https://issues.apache.org/jira/browse/THRIFT-357
> Project: Thrift
> Issue Type: Improvement
> Components: Library (C++)
> Reporter: Anthony Giardullo
> Priority: Minor
> Attachments: buffer_limit.patch
>
>
> This patch helps to reduce the amount of memory allocated by
> TNonBlockingServer. It uses a configurable limit on the number of idle
> connections to keep around, and has a configurable limit on the amount of
> memory to keep allocated in the readBuffer when the connection is closed.
> This fix is in use at Facebook and has significantly reduced the amount of
> memory used by Scribe (https://sourceforge.net/projects/scribeserver/).
> See THRIFT-265 for another memory usage fix which reallocates input/output
> buffers every 512 reads/writes. THRIFT-265(and THRIFT-354) and this patch
> can be used together to tune the amount of memory used. The buffer_limit
> patch is especially useful for the case when there are many idle TConnections
> with large buffers allocated.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
