Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 39589200CDD for ; Mon, 7 Aug 2017 16:58:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 37CF9165785; Mon, 7 Aug 2017 14:58:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 74FDF165784 for ; Mon, 7 Aug 2017 16:58:03 +0200 (CEST) Received: (qmail 25525 invoked by uid 500); 7 Aug 2017 14:58:02 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 25514 invoked by uid 99); 7 Aug 2017 14:58:02 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Aug 2017 14:58:02 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 31B0DE96E8; Mon, 7 Aug 2017 14:58:02 +0000 (UTC) From: clebertsuconic To: dev@activemq.apache.org Reply-To: dev@activemq.apache.org References: In-Reply-To: Subject: [GitHub] activemq-artemis issue #1444: ARTEMIS-1326 testTimeOnTimedBuffer incorrect t... Content-Type: text/plain Message-Id: <20170807145802.31B0DE96E8@git1-us-west.apache.org> Date: Mon, 7 Aug 2017 14:58:02 +0000 (UTC) archived-at: Mon, 07 Aug 2017 14:58:04 -0000 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. ---