geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] [Created] (GERONIMO-6373) Expose HOWL flushPartialBuffer config via HOWLLog - useful under low concurrency
Date Tue, 17 Jul 2012 20:02:33 GMT
Gary Tully created GERONIMO-6373:
------------------------------------

             Summary: Expose HOWL flushPartialBuffer config via HOWLLog - useful under low
concurrency
                 Key: GERONIMO-6373
                 URL: https://issues.apache.org/jira/browse/GERONIMO-6373
             Project: Geronimo
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: transaction manager
    Affects Versions: 2.2.1
            Reporter: Gary Tully


HOWL XALogger supports flushPartialBuffers which is not configurable via Geronimo HOWLLog.
It is useful in the case of low concurrency.

It would be great to have this exposed in the HOWLLog constructor so that it be be configured.

{code}  /**
   * Indicates whether LogBufferManager should flush buffers
   * before they are full.
   * 
   * <p>Normally, buffers are flushed to disk only when
   * they become full.  In lightly loaded situations,
   * one or more threads may have to wait until the
   * flushSleepTime expires before the buffer is written.
   * In the worst case, a single thread is using the
   * log, and every put() with sync requested will
   * be delayed flushSleepTime ms before the buffer is
   * written.
   * 
   * <p>Setting flushPartialBuffers true will allow
   * the LogBufferManager to flush buffers to disk
   * any time the channel is not busy.  This improves
   * throughput in single threaded and lightly loaded
   * environments. 
   * 
   * <p>By default, this feature is disabled (false) to
   * provide compatability with earlier versions of
   * this library.
   */
  private boolean flushPartialBuffers = false;{code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message