This content has been marked as final.
Show 3 replies
-
1. Re: Selectors run in memory, not in the database
timfox Oct 26, 2005 6:20 AM (in response to ovidiu.feodorov)"ovidiu.feodorov@jboss.com" wrote:
Currently, a channel state keeps non-reliable message references in memory and reliable message references in database. This should change, reliable references must be cached in memory too, for performance reasons. Selectors will only run in memory. Database serves only two purposes:
1. recovery
2. storage for message bodies.
Adrian keeps repeating this for a while ...
Great - this will give a performance hit too.
Right now, when a lot of consumers are created on a queue at the same time, it takes ages. This is because they are all hitting the db to get the list of undelivered messages.
This a major bottleneck right now. -
2. Re: Selectors run in memory, not in the database
timfox Oct 26, 2005 7:13 AM (in response to ovidiu.feodorov)"timfox" wrote:
Great - this will give a performance hit too."timfox" wrote:
What I meant was, it would give a performance boost :)