Just as a reference, no-sync with AIO:


Producer ActiveMQQueue[TEST], thread=0 Produced: 500000 messages
Producer ActiveMQQueue[TEST], thread=0 Elapsed time in second : 124 s
Producer ActiveMQQueue[TEST], thread=0 Elapsed time in milli second :
124739 milli seconds


I'm not arguing how safe is to use either, but on my crash tests the
messages weren't lost if I waited some time before killing the server.


IAIO with no-sync probably has a higher level of guarantees of being
actually on the disk in case of crashes.. but if the user don't need
syncs, that's a rock & roll possibility.

On Thu, Feb 2, 2017 at 6:51 PM, Clebert Suconic
<[email protected]> wrote:
> On Thu, Feb 2, 2017 at 6:51 PM, Clebert Suconic
> <[email protected]> wrote:
>> WOW... if you disable persistence.. (in case you don't actually need
>> syncs every time).. this thing kicks some (put your favorite word
>> here)...
>
>
> I mean.. if you disable syncs on the journal...
>
>
> no-syncs on anything else won't run as fast as mapped.
>>
>>
>> on a temporary branch I"m working before putting this on master:
>>
>>
>>
>> in one screen:
>>
>> ./artemis consumer --message-count 500000
>>
>>
>>
>> and on another screen:
>>
>> ./artemis producer --message-count 500000
>>
>>
>>
>> #notice! the producer is still synchronizing, meaning we could disable
>> sync on producer as well:
>>
>>
>> journal-type = MAPPED, sync=false:
>> Producer ActiveMQQueue[TEST], thread=0 Produced: 500000 messages
>> Producer ActiveMQQueue[TEST], thread=0 Elapsed time in second : 36 s
>> Producer ActiveMQQueue[TEST], thread=0 Elapsed time in milli second :
>> 36345 milli seconds
>>
>>
>> You Rock @Francesco!
>>
>>
>> On Thu, Feb 2, 2017 at 1:44 PM, Clebert Suconic
>> <[email protected]> wrote:
>>> On Thu, Feb 2, 2017 at 1:43 PM, Clebert Suconic
>>> <[email protected]> wrote:
>>>> I always had requests to spin of the journal as a separate project.
>>>>
>>>
>>>
>>> I mean.. these were always personal requests...
>>
>>
>>
>> --
>> Clebert Suconic
>
>
>
> --
> Clebert Suconic



-- 
Clebert Suconic

Reply via email to