Yes you can go ahead.
Thanks a lot for the fix.
Olivier
-Original Message-
From: Rob Godfrey
Sent: lundi 29 octobre 2018 16:16
To: users@qpid.apache.org
Subject: Re: [Broker-J] JDBC message store performance
Hi Olivier,
I'm not terribly surprised... I've not tested extens
commits in the JDBC store might instead be
> > >>> for the
> > >>> remove() method on StoredJDBCMessage to (rather than immediately
> > >>> commit the message
> > >>> delete) schedule the message removal to be picked up by the next
> >
Hello Rob,
I modified your patch to set a minimum batch size of 10 but didn't see any
improvement in the overall throughput...
Olivier
-Original Message-
From: Rob Godfrey
Sent: mardi 2 octobre 2018 18:08
To: users@qpid.apache.org
Subject: Re: [Broker-J] JDBC message store perfor
nimum batch size of 10 or whatever and see
if you get a further speedup.
-- Rob
> Olivier
>
> -Original Message-
> From: Rob Godfrey
> Sent: mardi 25 septembre 2018 13:20
> To: users@qpid.apache.org
> Subject: Re: [Broker-J] JDBC message store performance
>
period?
Olivier
-Original Message-
From: Rob Godfrey
Sent: mardi 25 septembre 2018 13:20
To: users@qpid.apache.org
Subject: Re: [Broker-J] JDBC message store performance
And now with a fix to allow the system tests to pass consistently
https://issues.apache.org/jira/secure/attachment
e we schedule the commit but don't actually force
>>> the sync to disk on message deletion).
>>>
>>> -- Rob
>>>
>>> On Mon, 17 Sep 2018 at 14:55, VERMEULEN Olivier <
>>> olivier.vermeu...@murex.com> wrote:
>>>
>>>
sage deletion).
>>
>> -- Rob
>>
>> On Mon, 17 Sep 2018 at 14:55, VERMEULEN Olivier <
>> olivier.vermeu...@murex.com> wrote:
>>
>>> Ok then I missed something.
>>> Whan/Where is the reference-counting you were talking about in your
>>
Hello Rob,
I think there is something wrong with your patch, it only contains the git-diff
manual...
Olivier
-Original Message-
From: Rob Godfrey
Sent: mercredi 19 septembre 2018 09:31
To: users@qpid.apache.org
Subject: Re: [Broker-J] JDBC message store performance
I'm on vac
Rob Godfrey
> Sent: mercredi 19 septembre 2018 01:23
> To: users@qpid.apache.org
> Subject: Re: [Broker-J] JDBC message store performance
>
> As an alternative approach, how about the (totally untested) patch I've
> attached to QPID-8242 [1]
>
> Rather than trying to conso
Thanks a lot Rob, I'll try to test that next week.
Olivier
-Original Message-
From: Rob Godfrey
Sent: mercredi 19 septembre 2018 01:23
To: users@qpid.apache.org
Subject: Re: [Broker-J] JDBC message store performance
As an alternative approach, how about the (totally untested)
lt;
> olivier.vermeu...@murex.com> wrote:
>
>> Ok then I missed something.
>> Whan/Where is the reference-counting you were talking about in your first
>> mail happening?
>>
>> Olivier
>>
>> -Original Message-----
>> From: Rob Godfrey
>
l Message-
> From: Rob Godfrey
> Sent: lundi 17 septembre 2018 14:05
> To: users@qpid.apache.org
> Subject: Re: [Broker-J] JDBC message store performance
>
> Hi Olivier,
>
> the approach you are attempting will not work for the reasons I described
> previously. If the
Ok then I missed something.
Whan/Where is the reference-counting you were talking about in your first mail
happening?
Olivier
-Original Message-
From: Rob Godfrey
Sent: lundi 17 septembre 2018 14:05
To: users@qpid.apache.org
Subject: Re: [Broker-J] JDBC message store performance
Hi
/jdbc-message-store-commits
>
> Regards,
> Olivier
>
> -Original Message-
> From: Rob Godfrey
> Sent: vendredi 14 septembre 2018 16:06
> To: users@qpid.apache.org
> Cc: AYOUBI Ali
> Subject: Re: [Broker-J] JDBC message store performance
>
> On Fri, 14 Sep
;m surely are)
https://github.com/apache/qpid-broker-j/compare/master...overmeulen:feature/jdbc-message-store-commits
Regards,
Olivier
-Original Message-
From: Rob Godfrey
Sent: vendredi 14 septembre 2018 16:06
To: users@qpid.apache.org
Cc: AYOUBI Ali
Subject: Re: [Broker-J] JDBC message store
On Fri, 14 Sep 2018 at 15:30, VERMEULEN Olivier
wrote:
> Hello,
>
> We ran a performance test with a bunch of brokers and an Oracle database
> to store the messages.
> We noticed that the database was a bit overloaded with commits.
> Looking at the logs we saw that sending a message was triggerin
Hello,
We ran a performance test with a bunch of brokers and an Oracle database to
store the messages.
We noticed that the database was a bit overloaded with commits.
Looking at the logs we saw that sending a message was triggering 1 commit for 3
operations (QPID_QUEUE_ENTRIES, QPID_MESSAGE_META
17 matches
Mail list logo
