Beefy Boxes and Bandwidth Generously Provided by pair Networks
No such thing as a small change

Re: 64-bit architecture a memory hog for Apache/mod_perl?

by Elian (Parson)
on Jan 12, 2006 at 14:57 UTC ( #522705=note: print w/replies, xml ) Need Help??

in reply to 64-bit architecture a memory hog for Apache/mod_perl?

This isn't much of a surprise. In general, moving an application from a 32 to a 64 bit architecture machine will mean more memory usage, and 60% sounds about right.

While the memory used by strings and floating point data generally won't change in size, integers and pointers are now twice as big as they used to be, and perl makes use of a lot of integers and pointers internally. Going to a 64 bit architecture also means that the way some data structures are packed together changes and makes them a bit bigger on top of the extra memory needed for the larger pointers and integers.

This is true of any language, not just perl. Do a 64-bit build of python or ruby, or recompile your C program to be fully 64-bit, and you'll see the same sort of memory usage increase.

Basically assume a move to a 64 bit platform means you need twice as much memory on the system for equivalent performance. That's a bit of an over-estimate, but it should see you through OK, and memory's reasonably cheap.

  • Comment on Re: 64-bit architecture a memory hog for Apache/mod_perl?

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://522705]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others chanting in the Monastery: (6)
As of 2021-06-18 10:51 GMT
Find Nodes?
    Voting Booth?
    What does the "s" stand for in "perls"? (Whence perls)

    Results (89 votes). Check out past polls.