[
https://issues.jboss.org/browse/RF-11156?page=com.atlassian.jira.plugin.s...
]
Juraj Huska commented on RF-11156:
----------------------------------
Some performance tips I have found:
- Start the consumer before you start the producer so that the initial messages do not
need to queue.
- Use a ConnectionConsumer to process messages concurrently with a ServerSessionPool.
- Close resources (e.g. connections, session objects, producers, consumers) when finished
with them.
- DUPS_OK_ACKNOWLEDGE and AUTO_ACKNOWLEDGE perform better than CLIENT_ACKNOWLEDGE.
- Use separate transactional sessions and non-transactional sessions for transactional and
non-transactional messages.
- Tune the Destination parameters: a smaller capacity increases message throughput; a
higher redelivery delay and lower redelivery limit reduces the overhead.
- Choose non-durable (NON_PERSISTENT) messages wherever appropriate to avoid the
persistency overhead.
- Set the TimeToLive value as low as feasible (default is for messages to never expire).
- Receive messages asynchronously with a MessageListener implementation.
- Choose the message type that minimizes memory overheads.
- Use 'transient' variables to reduce serialization overheads.
a4j:push Performance problem in CDI sample of push in showcase
--------------------------------------------------------------
Key: RF-11156
URL:
https://issues.jboss.org/browse/RF-11156
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: examples
Affects Versions: 4.1.0.Milestone1
Environment: richfaces-showcase 4.1.0-Snapshot, containers - JBoss AS 6 and 7
Reporter: Juraj Huska
Assignee: Juraj Huska
Fix For: 4.1.0.Milestone2
When there is more than 5 consumers windows, it causes performance problems(take up to 20
seconds to render message on consumer), at least from the beginning, after some messsages
like 3-4 the performance is improved on AS 7.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira