[Users] Why do I TPS can only reach 300.

[Christophe DENEUX [via Petals Forums]]

All components process their messages using a pool of message acceptors and a
pool of message processors. A message is accepted by a message acceptor
before to be processed by a message processor.

So, your TPS is mainly driven by the number of available message processors
and secondly by the number of message acceptor.

I recommend you to:
  - define the nominal number of messages you want to process concurrently
by a component. So use this value as the core size of the processor pool.
  - define the max number of messages and use it as the value as the max
size of the processor pool.
  - the configuration of the acceptor pool depends on response time of your
service. More the response time is small, more the acceptor pool size should
be large.
  - realize several tries with different values to adjust them.

As each message processor is a thread, choosing a too big value for the core
pool size can decrease performances because of too context switchs at
micro-processor level.

-----
Christophe DENEUX
PetalsLink
CTO
_______________________________________________
If you reply to this email, your message will be added to the discussion below:
http://forum.petalslink.com/Why-do-I-TPS-can-only-reach-300-tp3643553p3812061.html
To start a new topic under Users (get help, provide help), email ml-node+s974793n2681628h42 at n3.nabble.com
To unsubscribe from Users (get help, provide help), visit http://forum.petalslink.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=2681628&code=dXNlcnNAZm9ydW0ucGV0YWxzbGluay5vcmd8MjY4MTYyOHwtOTE3MDU0NjU4
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://forum-list.petalslink.org/pipermail/users/attachments/20120309/2e1c8a98/attachment.htm>