A new feature batching asynchronous messages for client/server mode is introduced in latest svn code. The client will hold asynchronous messages until commit/rollback/or any other synchronized messages. It's user transparent, and easy to configure. To experience batched messages mode, please:
1. check out latest svn code.
2. configure batched mode -- oc.configure().clientServer().batchMessages(true);
3. configure maxBatchQueueSize if you'd like. Noted that batching messages will consume more memory than non-batched mode. To control memory cosumption, db4o provides configuration for maximum queue size. If the queued messages is greater than maxBatchQueueSize, all batched messages are flushed to the server. Using oc.configure().clientServer().maxBatchQueueSize(maxSize) to configure it.
It's supposed to improve the performance of some operations, like inserting new objects to database. Please take a try and give us your feedback. Your suggestions/comments/thoughts are highly appreicated!
Thanks in adavance!
-
Posted by Anonymous on 3/20/2010 6:40 PM
Welcome to the February newsletter! Version 6.1 Makes db4o Even More Scalable Product Roadmap 2007 Drafted
-
Posted by Anonymous on 3/20/2010 6:40 PM
Newsletter #28 - db4o 6.1 erhöht Skalierbarkeit; Roadmap 2007 Willkommen zum Februar Newsletter! K U
-
Posted by Anonymous on 3/20/2010 6:40 PM
欢迎来到db4o 2月通讯! K U D O O F T H E M O N T H "我已经在.NET上使用db4o大概一年时间,如果你还未使用db4o,真的是一种遗憾...db4o能够帮你节省50%的开发时间.这还是比较保守的估计."
-
Posted by mikewinny on 3/20/2010 6:40 PM
aychronized?! i think i can read that better if i pretend it says 'asynchronous'
Loading, please waiting...