activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From clebertsuconic <...@git.apache.org>
Subject [GitHub] activemq-artemis issue #1444: ARTEMIS-1326 testTimeOnTimedBuffer incorrect t...
Date Mon, 07 Aug 2017 14:58:02 GMT
Github user clebertsuconic commented on the issue:

    https://github.com/apache/activemq-artemis/pull/1444
  
    the point of the TimedBuffer is to limit the writes you can send to storage at a limit....
you write once.. flush... next time you write it must be in the configured timing...
    
    the only reason why the flush could be flushed before time is if the buffer is full, and
that is currently contemplated... anything else will be sending more writes (and possibly
flushes) than what the device is capable of handling....
    
    
    again.. if Mapped works differently, then don't use TimedBuffer.. but you can't change
this semantic here.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message