February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Closed: (JBMESSAGING-313) INVM persistent message optimisation

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-313?page=all ] Ovidiu Feodorov closed JBMESSAGING-313. --------------------------------------- Resolution: Duplicate Issue > INVM persistent message optimisation > ------------------------------------ > > Key: JBMESSAGING-313 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-313 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.0.GA > > Original Estimate: 1 day > Remaining Estimate: 1 day > > For persistent messages sent in vm, the message gets converted to a byte[] before db storage, it then gets converted back to a payload on recepipt - this is unnecessary - for the invm case. We should deal with it optimally. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-162) Consider implementing different message delivery optimisations

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-162?page=all ] Ovidiu Feodorov closed JBMESSAGING-162. --------------------------------------- Resolution: Duplicate Issue > Consider implementing different message delivery optimisations > -------------------------------------------------------------- > > Key: JBMESSAGING-162 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-162 > Project: JBoss Messaging > Issue Type: Feature Request > Components: JMS Facade > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Minor > Fix For: 1.2.0.GA > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Consideri implementing different different message delivery optimisations. > e.g. client side buffering > multicast (both reliable and unreliable) > these could be selected by using special, jboss specific ack modes -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-246) Optimise browsing

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-246?page=all ] Ovidiu Feodorov closed JBMESSAGING-246. --------------------------------------- Resolution: Duplicate Issue > Optimise browsing > ----------------- > > Key: JBMESSAGING-246 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-246 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.0.GA > > Original Estimate: 4 days > Remaining Estimate: 4 days > > Currently browsing is inefficient and copies the entire set of message references. Instead we should use the deque iterator + the deliveries iterator. > We should also investigate activating the browsing interceptor to batch messages. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-162) Consider implementing different message delivery optimisations

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-162?page=all ] Ovidiu Feodorov updated JBMESSAGING-162: ---------------------------------------- Fix Version/s: 1.2.0.GA (was: 1.2.1) > Consider implementing different message delivery optimisations > -------------------------------------------------------------- > > Key: JBMESSAGING-162 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-162 > Project: JBoss Messaging > Issue Type: Feature Request > Components: JMS Facade > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Minor > Fix For: 1.2.0.GA > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Consideri implementing different different message delivery optimisations. > e.g. client side buffering > multicast (both reliable and unreliable) > these could be selected by using special, jboss specific ack modes -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-307) Down cache optimisation

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-307?page=all ] Ovidiu Feodorov updated JBMESSAGING-307: ---------------------------------------- Fix Version/s: 1.2.0.GA (was: 1.2.1) > Down cache optimisation > ----------------------- > > Key: JBMESSAGING-307 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-307 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.0.GA > > Original Estimate: 3 days > Remaining Estimate: 3 days > > If there are no persistent messages in storage then when paging we can avoid flushing the downCache and loading from the db > and just transfer from the downcache to the in memory list when loading -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-313) INVM persistent message optimisation

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-313?page=all ] Ovidiu Feodorov updated JBMESSAGING-313: ---------------------------------------- Fix Version/s: 1.2.0.GA (was: 1.2.1) > INVM persistent message optimisation > ------------------------------------ > > Key: JBMESSAGING-313 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-313 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.0.GA > > Original Estimate: 1 day > Remaining Estimate: 1 day > > For persistent messages sent in vm, the message gets converted to a byte[] before db storage, it then gets converted back to a payload on recepipt - this is unnecessary - for the invm case. We should deal with it optimally. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-246) Optimise browsing

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-246?page=all ] Ovidiu Feodorov updated JBMESSAGING-246: ---------------------------------------- Fix Version/s: 1.2.0.GA (was: 1.2.1) > Optimise browsing > ----------------- > > Key: JBMESSAGING-246 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-246 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.0.GA > > Original Estimate: 4 days > Remaining Estimate: 4 days > > Currently browsing is inefficient and copies the entire set of message references. Instead we should use the deque iterator + the deliveries iterator. > We should also investigate activating the browsing interceptor to batch messages. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-268) Convert destinations to ints in message instance

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-268?page=all ] Ovidiu Feodorov updated JBMESSAGING-268: ---------------------------------------- Fix Version/s: 1.2.0.GA (was: 1.2.1) > Convert destinations to ints in message instance > ------------------------------------------------ > > Key: JBMESSAGING-268 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-268 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.0.GA > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Destination implementations JBossQueue and JBossTopic are currently not much more than just Strings identifiers. > When sending a message the destination (and possibly the replyto) need to be serialized with the message. > If the Destinations are just identifiers then they could represented as ints making there less bytes to serialize. > This could be significant for destinations with long names, e.g. 100 bytes -> 4 bytes (per message) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBMESSAGING-313) INVM persistent message optimisation

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-313?page=all ] Ovidiu Feodorov reopened JBMESSAGING-313: ----------------------------------------- > INVM persistent message optimisation > ------------------------------------ > > Key: JBMESSAGING-313 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-313 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > For persistent messages sent in vm, the message gets converted to a byte[] before db storage, it then gets converted back to a payload on recepipt - this is unnecessary - for the invm case. We should deal with it optimally. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBMESSAGING-307) Down cache optimisation

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-307?page=all ] Ovidiu Feodorov reopened JBMESSAGING-307: ----------------------------------------- > Down cache optimisation > ----------------------- > > Key: JBMESSAGING-307 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-307 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.1 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > If there are no persistent messages in storage then when paging we can avoid flushing the downCache and loading from the db > and just transfer from the downcache to the in memory list when loading -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2007