[Design of Messaging on JBoss (Messaging/JBoss)] - Re: LinkedList Factor on the Journal...
by clebert.suconic@jboss.com
Few solutions I have thought for this:
I - Separate CurrentFile by Destination type.
We would add/delete records per destination.
We would still be able to commit without a problem
I have written this code already, and it has one side effect. If the customer has 1000 lazy destinations you will have 1000 opened files, what is not possible on AIO.
II - Separate CurrentFile by Destination speed.
We could have a destination configured as Lazy, what would keep records in separate.
We would still be able to commit without a problem, as any commit record aways carries the filesIds and number of elements used.
This would use the code I already wrote on (i).
III - Depending on the number of dependencies found on Reclaiming, we could start a FullReclaiming logic (think of a fullGC) that would move records around, facilitating how the files are reclaiming.
This has performance implications. It's listed here just as a brain storm.
I think option II would be a reasonable one.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167655#4167655
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167655
16 years, 5 months