qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Stitcher (JIRA)" <qpid-...@incubator.apache.org>
Subject [jira] Resolved: (QPID-1879) The client library uses a new thread for every connection
Date Thu, 28 May 2009 05:19:45 GMT

     [ https://issues.apache.org/jira/browse/QPID-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Andrew Stitcher resolved QPID-1879.

    Resolution: Fixed

Don't use a thread for every new client Connection
    - By default the max number of threads now used for network io
      is the number of cpus available.
    - This can be overridden with the QPID_MAX_IOTHREADS environment
      variable or the config file

> The client library uses a new thread for every connection
> ---------------------------------------------------------
>                 Key: QPID-1879
>                 URL: https://issues.apache.org/jira/browse/QPID-1879
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Client
>    Affects Versions: M1, M2, M2.1, M3, M4, 0.5
>            Reporter: Andrew Stitcher
>            Assignee: Andrew Stitcher
>             Fix For: 0.6
> This is actually slightly worse than just using a new thread per broker connection as
it also uses a new Poller for every Connection and the Poller is fairly hefty and includes
a number of fds for its own use. This multiplies the client fd use for clients with many Connections.
> It's not really acceptable that opening 1000 connections should create 1000 threads.
> It should be noted that this isn't the only aspect of the client library that uses excessive
numbers of threads, lets knock them off one by one

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org

View raw message