ActiveMQ
  1. ActiveMQ
  2. AMQ-3646

Allow KahaDB to run without disk syncs, higher through put without the jms persistence guarantee

    Details

      Description

      When using the broker as a buffer for persistent data, large bursts or additions, periodic batch removes, we want to become disk bound. Waiting for disk syncs causes unnecessary pauses. If the JMS durability guarantee is not needed, it should be possible to execute without disk syncs. Syncing only on shutdown.

        Activity

        Hide
        Gary Tully added a comment -

        fix in http://svn.apache.org/viewvc?rev=1222705&view=rev

        A checkpoint won't disk sync when setEnableJournalDiskSyncs=false on kahaDB. Checkpoint and cleanup can be disabled altogether with a period of 0. The broker jmx view gc() operation will do a persistence adapter checkpoint/cleanup so it is possible to manually force a gc of the store.

        Show
        Gary Tully added a comment - fix in http://svn.apache.org/viewvc?rev=1222705&view=rev A checkpoint won't disk sync when setEnableJournalDiskSyncs=false on kahaDB. Checkpoint and cleanup can be disabled altogether with a period of 0. The broker jmx view gc() operation will do a persistence adapter checkpoint/cleanup so it is possible to manually force a gc of the store.

          People

          • Assignee:
            Gary Tully
            Reporter:
            Gary Tully
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development