Hi Maarten
Kinda.
MapMessages are significantly more expensive but no real surprise there.
I upgraded the machine and did significant optimising on the GC, paying
particular attention to parallel / conc mark sweep
eg
-XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:+CMSIncrementalPacing
-XX:CMSIncrementalDutyCycleMin=0
or
-XX:+UseParallelGC"
or
-XX:-UseParallelOldGC
I couldn't find any good info on what GC settings people have used for their
platform.... but working with known test cases and measuring over multiple
10,000's tests helped to determine optimum settings on mine.
what are you seeing?
thanks
Adrian
Maarten_D wrote:
>
> Hi Adrian,
> Have you made any progress on this issue? I believe I'm running into the
> same things occasionally.
> Regards,
> Maarten
>
>
> Adrian A wrote:
>>
>> Setting them to MapMessages (what I am using) makes it even worse:
>>
>> //TextMessage message = session.createTextMessage(createMessageText(i));
>> MapMessage message = session.createMapMessage();
>> message.setJMSType("blahasdadasdsd");
>> message.setLong("test1",2222);
>> message.setLong("test2",2222);
>> message.setLong("test3",2222);
>> message.setLong("test4",2222);
>> message.setLong("test5",2222);
>>
>> by 10 to 20 times worse.
>>
>>
>> Adrian A wrote:
>>>
>>> long start = System.currentTimeMillis();
>>> producer.send(message);
>>> long stop = System.currentTimeMillis();
>>>
>>
>>
>
>
--
View this message in context:
http://old.nabble.com/Slow-sending-of-messages-tp26849964p27611873.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
