[ https://jira.jboss.org/jira/browse/JBMESSAGING-1427?page=com.atlassian.ji... ] Clebert Suconic updated JBMESSAGING-1427: ----------------------------------------- Attachment: optimize-lazy-destinations.patch This patch, with a proposed solution can be applied to r4753 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1427?page=com.atlassian.ji... ] Tim Fox commented on JBMESSAGING-1427: -------------------------------------- I don't understand the proposal here, more explanation is required. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1427?page=com.atlassian.ji... ] Tim Fox commented on JBMESSAGING-1427: -------------------------------------- I don't believe the lazy destination approach will work, since the user will need to know in advance which destinations are lazy and which are not, which may not always be possible. Also if there is a slow and a fast consumer on a queue for a long time, and the slow consumer only acks intermittently, you still have the same problem. Instead what we need to do is create a compactor. The compactor is an extension of the reclaimer. Files can be marked as "tocompact" by the compactor if more than X% of the file is not needed. A separate compactor thread then checks the "tocompact" flag and compacts multiple files into smaller number -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1427?page=com.atlassian.ji... ] Clebert Suconic commented on JBMESSAGING-1427: ---------------------------------------------- I was playing with some scenarios, and I'm not sure if the compactor would work also. I have been playing with examples and it would be possible to create scenarios where compacting is useless... Besides we would have a lot of complexity on reallocating files and hole-detection on the transaction summary. In my opinion would be better to have a currentFile for each address on the journal. It would be the same as having one journal for each address but without loosing transactionality when sending to multiple transactions. (Which would be my initial approach with a slight variation). This option would have a better performance as we wouldn't have the compactor competing with Adds. There won't simply be a need to compact anything. I will bring this discussion online on our next meeting and make a post on dev forums afterwards. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1427?page=com.atlassian.ji... ] Tim Fox commented on JBMESSAGING-1427: -------------------------------------- Yes please move on from the idea of one file per journal! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1427?page=com.atlassian.ji... ] Clebert Suconic updated JBMESSAGING-1427: ----------------------------------------- Attachment: backup.patch -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1427?page=com.atlassian.ji... ] Clebert Suconic updated JBMESSAGING-1427: ----------------------------------------- Attachment: (was: backup.patch) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1427?page=com.atlassian.ji... ] Clebert Suconic updated JBMESSAGING-1427: ----------------------------------------- Comment: was deleted -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1427?page=com.atlassian.ji... ] Tim Fox updated JBMESSAGING-1427: --------------------------------- Fix Version/s: 2.0.0.CR1 (was: 2.0.0 Beta) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1427?page=com.atlassian.ji... ] Tim Fox updated JBMESSAGING-1427: --------------------------------- Issue Type: Task (was: Feature Request) Priority: Major (was: Critical) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1427?page=com.atlassian.ji... ] Clebert Suconic updated JBMESSAGING-1427: ----------------------------------------- Issue Type: Feature Request (was: Task) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1427?page=com.atlassian.ji... ] Tim Fox updated JBMESSAGING-1427: --------------------------------- Fix Version/s: 2.0.0 (was: 2.0.0.beta5) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira