Comment 3 for bug 109114
Revision history for this message
| John A Meinel (jameinel) wrote Re: commit holds whole files in memory | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
demo site
(Get the code!)
I just wanted to add something to this bug.
On IRC, Treeform pointed me to a text file which was only 80MB in size, but had 2.6M lines.
When trying to commit, I let it get to about 700MB (I only have 1GB of ram) before I kill it because it makes my machine unusable.
I'll try to run it on another machine and give the final peak vmstat.
But at a minimum, we seem to have almost 10 copies of it in RAM. We've argued about needing 3 for merge, but commit should not need 10. Especially since this is a plain "bzr init; bzr add; bzr commit". I could understand having 2 copies (say it is a string and we are splitting it into a list, etc).
But for "init; add; commit" we don't even need to run diff.