[jira] [Assigned] (GERONIMO-6373) Expose HOWL flushPartialBuffer config via HOWLLog - useful under low concurrency

2012-07-24 Thread Guillaume Nodet (JIRA)

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

Guillaume Nodet reassigned GERONIMO-6373:
-

Assignee: Guillaume Nodet  (was: David Jencks)

> 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
>Assignee: Guillaume Nodet
> Attachments: GERONIMO-6372.patch
>
>
> 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.
>* 
>* 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.
>* 
>* 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. 
>* 
>* 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




[jira] [Assigned] (GERONIMO-6373) Expose HOWL flushPartialBuffer config via HOWLLog - useful under low concurrency

2012-07-17 Thread David Jencks (JIRA)

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

David Jencks reassigned GERONIMO-6373:
--

Assignee: David Jencks

> 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
>Assignee: David Jencks
> Attachments: GERONIMO-6372.patch
>
>
> 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.
>* 
>* 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.
>* 
>* 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. 
>* 
>* 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