I also noticed while running it from within Mac OS X during a "bzr get" operation that the bzr binary used up to 2 GB of RAM at its peak. Why would bzr load this much data into memory at once and not do more of a stream-like operation?
I also noticed while running it from within Mac OS X during a "bzr get" operation that the bzr binary used up to 2 GB of RAM at its peak. Why would bzr load this much data into memory at once and not do more of a stream-like operation?