monotone - Bugs: bug #26595, put_revision and pull (and likely...
You are not allowed to post comments on this tracker with your current authentication level.
bug #26595: put_revision and pull (and likely commit, too) scale with tree size instead of changeset size
Submitter: | Patrick Georgi <oxygene> | ||
Submitted: | Sat 16 May 2009 04:40:37 PM UTC | ||
Category: | performance | Severity: | 3 - Normal |
Item Group: | feature request | Status: | Fixed |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Closed | ||
mtn version --full: | applies at least to 0.36 - 0.44. |
Tue 09 Feb 2010 11:45:16 PM UTC, comment #2: |
Timothy Brownawell <tbrownaw> |
Tue 26 Jan 2010 08:54:39 PM UTC, comment #1: Some more information:
|
Patrick Georgi <oxygene> |
Sat 16 May 2009 04:40:37 PM UTC, original submission:
The scalability problem comes from roster handling.
|
Patrick Georgi <oxygene> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 2 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2010-02-09 | tbrownaw | Status | None | Fixed | |
Open/Closed | Open | Closed |
Powered by Savane 3.13-4b48.
Corresponding source code
This particular instance should be fixed in 85496c3f1a001e20bd3318a80acf9ab848ee0bd1 . Only deltas for non-merge revisions can be sped up this way.
Note that there are other unavoidable operations that still need to scale by tree size, like calculating/verifying the manifest_id of a revision or writing out the full roster text for the head revision to the db.