Joe Niederberger wrote:
> Does anyone know if one can have 64bit perl use 64 bit addressing (to make
> use of >4GB RAM) but still use 32-bit INTs etc (to keep footprint from
> getting
> large)?
This is the default on windows x64.
I should add - if anyone can answer this question - would it be a good idea
to do
so even if possible?
Thanks,
Joe Niederberger
> Does anyone know if one can have 64bit perl use 64 bit addressing (to make
> use of >4GB RAM) but still use 32-bit INTs etc (to keep footprint from
> getting
> larg
Does anyone know if one can have 64bit perl use 64 bit addressing (to make
use of >4GB RAM) but still use 32-bit INTs etc (to keep footprint from
getting
large)?
Thanks,
Joe N.
Well, some poking aronud by the sysadmins and they found teh perl
was compiled with
> MYMALLOC PERL_MALLOC_WRAP USE_64_BIT_ALL USE_64_BIT_INT USE_FAST_STDIO
> USE_LARGE_FILES USE_PERLIO
So it was using 64 bit variables for INT and maybe some other uneeded
things.
So that might be a big part of it
On 12/20/2009 09:40 AM, Joe Niederberger wrote:
32bit: SIZE=45M RES=32M
64bit: SIZE=95M RES=45M
Do these look reasonable? Should I worry?
Good question. While I haven't made the jump to 64bit for my web
machines there are lots of memory related things that double in size
when you do s
Hello,
I'm in process of moving a mod_perl/apache1.3 application from
32bit to 64bit architectures. I am not a sysadmin, but rather the app
programmer.
But I'm surprised by the dramatic leap in httpd process sizes. Here are
"typical" SIZE/RES figures:
32bit: SIZE=45M RES=32M
64bit: SIZE=
