Menu
▾
▴
Re: [Quickfixj-users] Rolling Message store?
|
From: Colin C. <col...@he...> - 2007-06-19 12:21:47
|
To perform well you need to get the messages to disk asap and then worry about having them stored in a more useful structured way. Engine startup would flush messages from this transaction log into the proper store. I'd recommend HOWL as a transaction log, it does what it says on the tin... http://howl.objectweb.org/ Colin. http://hermesjms.com _____ From: qui...@li... [mailto:qui...@li...] On Behalf Of Vladimir Kvasov Sent: 19 June 2007 07:26 To: qui...@li... Subject: Re: [Quickfixj-users] Rolling Message store? Brad, I tried to use hsqldb (embedded mode) to perform data processing once. sql queries simplified code a little bit but there was a significant difference in performance compared to processing based on ArrayLists. hsqldb version was much slower. So I'd recommend to write some pilot code to perform load tests before choosing to use hsqldb. wbr _________________________________ Vladimir Kvasov Trading & Market Making Rates Technology Deutsche Bank +7 495 9812289 "Brad Harvey" <Bra...@gb...> Sent by: qui...@li... 19.06.2007 02:12 Please respond to qui...@li... To <qui...@li...> cc Subject Re: [Quickfixj-users] Rolling Message store? QuickFIX/J Documentation: http://www.quickfixj.org/documentation/ QuickFIX/J Support: http://www.quickfixj.org/support/ I wonder how hsqldb with a cached table would compare in terms of performance and reliability? Should be able to plug it into the existing jdbc store. If you run hypersonic in embedded mode it wouldn't add much system admin overhead over the file store. Brad. -----Original Message----- From: qui...@li... [mailto:qui...@li...] On Behalf Of Steve Bate Sent: Tuesday, 19 June 2007 4:13 AM To: qui...@li... Subject: Re: [Quickfixj-users] Rolling Message store? QuickFIX/J Documentation: http://www.quickfixj.org/documentation/ QuickFIX/J Support: http://www.quickfixj.org/support/ > I suspect that for fix resend purposes i'll never need more than the > last 10 minutes of messages. Is there a standard MessageStore > implementation that either just forgets older messages, or a way of > getting FileStore to roll old messages over (say every day)? This > would allow old messages to be archived or deleted without affecting a running app. There's not a rolling file implementation for the message store. > If not, would such a message store be a useful addition to the codebase? > I'm thinking of a MemoryStore with a time limit threshold, or a > FileStore with various rolling configuration options similar to log4j. I'm not sure how useful a rolling store would be. However, there's room for improvement in the caching of the messages for resend. Currently, the file store loads all messages into memory (using MemoryStore). That can slow down server start time and can consume a lot of memory for long, active sessions. Another option might be to use something like JBossCache or EhCache (or similar) to store the messages with a backing file but configure the cache to delete messages that are old than a specified age. We would need to do some experimentation to be sure the performance is good enough. Steve ------------------------------------------------------------------------ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Quickfixj-users mailing list Qui...@li... https://lists.sourceforge.net/lists/listinfo/quickfixj-users ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Quickfixj-users mailing list Qui...@li... https://lists.sourceforge.net/lists/listinfo/quickfixj-users --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. |