You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "james (JIRA)" <ji...@apache.org> on 2014/02/10 20:55:21 UTC

[jira] [Created] (AMQ-5039) allow for thread pooling with multi kahadb persistence

james created AMQ-5039:
--------------------------

             Summary: allow for thread pooling with multi kahadb persistence
                 Key: AMQ-5039
                 URL: https://issues.apache.org/jira/browse/AMQ-5039
             Project: ActiveMQ
          Issue Type: Improvement
          Components: Message Store
    Affects Versions: 5.9.0
            Reporter: james
            Priority: Minor


I am probably using the multi KahaDB storage a bit differently than others, but i expect to be using many instances within my activemq broker.  As such, i noticed that the kahadb impl uses a bunch of threads per instance.  Some of this may be necessary, but the scheduled tasks at the least could most likely allow for sharing a Timer or ScheduledExecutorService instance.

Locations:
* Journal creates a Timer instance (even though Scheduler has a shared instance)
* MessageDatabase creates a dedicated checkpoint thread (which is essentially a scheduled task)
* DataFileAppender has a dedicated writer thread.  possibly harder to share.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)