2GB limit
John Arbash Meinel
john at arbash-meinel.com
Fri Oct 8 14:47:12 BST 2010
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 10/8/2010 1:09 AM, Maritza Mendez wrote:
>
>
> On Thu, Oct 7, 2010 at 8:41 PM, Martin Pool <mbp at canonical.com
> <mailto:mbp at canonical.com>> wrote:
>
>
> This problem isn't inherent to Windows but I think Windows is the only
> place where we don't use 64-bit addressing even when the system
> supports it.
>
>
>
> Aha. Now I think I see. Thanks. I will read some of the threads in
> which peole have tried to build for Windows x64 and see if I have any
> ideas. Thanks.
I think there are a couple of issues. One is that 'pack' is allocating
~5x the largest content. So auto-packing has a high peak memory requirement.
And 64-bit at least allows us to allocate more memory blocks. (So if
your machine has 4GB we aren't stuck at the 2GB barrier.)
The next issue will be handling content >2GB and then again at content
>4GB. The delta structures, etc, have certainly not been audited for
working correctly at that level. Note that 'content' may not be a single
file, because of how we combine texts, though it would be close to that
(within 2-4x sort of thing).
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkyvIOAACgkQJdeBCYSNAAOSQQCfT5ooJRRi7oYPm0t9NP3+OsB2
zQgAn2g1f32KoEcYifL08elLP28rjbg9
=FMtl
-----END PGP SIGNATURE-----
More information about the bazaar
mailing list