MemoryError with versionning 100+MB file
Alexander Belchenko
bialix at ukr.net
Fri Dec 21 11:40:29 GMT 2007
Forest Bond пишет:
> Hi,
>
> On Thu, Dec 20, 2007 at 04:23:55PM +0200, Alexander Belchenko wrote:
>> My coworker try to versionning 1GB disk ISO image, gzipped one has the size
>> about 120MB. He successfully commit 2 revisions and now stuck with
>> MemoryError while reading knit during commit.
>>
>> Is there possible to create some workaround now? These big files is purely
>> binary, is it possible to exclude read knit phase at all?
>
> Add swap space?
I did. But in facts absence of MemoryError does not mean that bzr is
usable for my tree (5 files, 2 of them 100+MB). After 4+ hours of
running commit operation I finally kill bzr process. Before this moment
`top` reports that bzr use 1000+MB memory, all physical (512MB) and
760MB of swap was in use. All the time hard disk working, i.e. swapping
data in and out.
It's will be nice to have some official info what the biggest size of
file/files bzr is able to handle depends on how many physical RAM your
computer has. Pretends that bzr is able to handle virtually any big file
if you have 4x big swap size -- is the way to nowhere.
More information about the bazaar
mailing list