History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: COR-776
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Critical Critical
Assignee: Unassigned
Reporter: Andrew Zhang
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
db4o Core

Client/Server performance problem when operating on complex object

Created: 24/Aug/07 11:20 AM   Updated: 18/Jul/08 02:57 PM
Component/s: Client/Server
Affects Version/s: None
Fix Version/s: Egypt

Time Tracking:
Original Estimate: Not Specified
Remaining Estimate: 0h
Time Spent - 8h
Time Spent: 8h
Time Spent - 8h

Order: 3
Iteration: 6
Original IDS Estimate: 1
Resolution Date: 31/Aug/07 06:28 AM
First Response Date: 31/Aug/07 06:28 AM
Labels:
Participants: Andrew Zhang and Richard Liang
Number of Attachments: 0
Number of Comments: 3


 Description  « Hide
"Inserting and deleting objects takes up to 20 times longer when the database server isn't on the same machine as the database client.
Especially object graphs, where the top level object provides a lot of child objects, are more than lame."

It's reported in the forum: http://developer.db4o.com/forums/thread/40705.aspx

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Andrew Zhang - 24/Aug/07 11:24 AM
Config batchMessages as true to see whether it improves the performance by following code:

Db4o.Configure().ClientServer().BatchMessages(true);

Andrew Zhang - 30/Aug/07 02:46 AM
The test case commits every change after every operation.

We suggest do batch commits, say, 1 commit after 100 operations.

Richard Liang - 31/Aug/07 06:28 AM
Waiting for verification