35 messages in org.apache.perl.modperlRe: compile problems
FromSent OnAttachments
BeberleDec 13, 2004 2:43 am 
Tom SchindlDec 13, 2004 4:02 am 
Reenen C KroukampDec 13, 2004 4:44 am 
BeberleDec 14, 2004 5:32 pm 
Joe SchaeferDec 14, 2004 6:49 pm 
BeberleDec 16, 2004 6:42 pm 
Joe SchaeferDec 16, 2004 8:44 pm 
Matthew BerkDec 16, 2004 11:05 pm 
Stas BekmanDec 17, 2004 8:11 am 
Barksdale, RayDec 17, 2004 8:57 am 
Joe SchaeferDec 17, 2004 10:27 am 
Stas BekmanDec 17, 2004 10:38 am 
Barksdale, RayDec 17, 2004 11:04 am 
Stas BekmanDec 17, 2004 11:25 am 
Barksdale, RayDec 17, 2004 1:04 pm 
Stas BekmanDec 17, 2004 1:19 pm 
Barksdale, RayDec 17, 2004 3:37 pm 
Stas BekmanDec 17, 2004 3:44 pm 
Matthew BerkDec 20, 2004 6:43 am 
Barksdale, RayDec 22, 2004 7:19 am 
Stas BekmanDec 22, 2004 12:27 pm 
Barksdale, RayDec 22, 2004 12:37 pm 
Stas BekmanDec 22, 2004 1:16 pm 
Barksdale, RayDec 22, 2004 2:01 pm 
Stas BekmanDec 22, 2004 2:22 pm 
Barksdale, RayDec 22, 2004 3:06 pm 
Stas BekmanDec 22, 2004 4:01 pm 
Barksdale, RayDec 28, 2004 2:50 pm 
Stas BekmanDec 28, 2004 3:01 pm 
Barksdale, RayDec 28, 2004 3:14 pm 
Stas BekmanDec 28, 2004 3:17 pm 
Barksdale, RayDec 28, 2004 3:50 pm 
Joe SchaeferDec 28, 2004 5:29 pm 
Barksdale, RayDec 29, 2004 8:59 am 
Stas BekmanDec 29, 2004 9:21 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: compile problemsActions...
From:Stas Bekman (st@stason.org)
Date:Dec 28, 2004 3:01:19 pm
List:org.apache.perl.modperl

Barksdale, Ray wrote:

OK, so it has something to do with 64-bit-ness. But I didn't understand. Was this problem seen on a 64-bit CPU or on a 32-bit CPU, but then code was compiled for 64-bit?

The problem (more of an observation at this point) was the apparent excessive memory usage of Apache2/mod_perl2 (64-bit build) on top of 64-bit Linux (RedHat Fedora Core 2 - AMD64 distribution).

We built perl/Apache/mod_perl/libapreq/etc/etc.... in the same fashion as we had for our 32-bit environment (again RedHat Fedora Core 2 - x86). The memory load was normal. We were not doing any crosscompiles of 64 to 32 or viceversa.

I had a brain fart. We (read "me") got crossed up on what -m64 caused gcc to do. I read the docs and understood this to cause gcc to force the usage of the additional registers on the opteron. This is the default behavior when building (note to self...) in the 64-bit environment. Also found that there is a -march=k8 option (again a default in 64-bit land).

As far as the memory usage problem I thought I was on to the source when I stripped my httpd binary and went from:

VIRT RES SHR 76232 3856 73m to 17524 2064 15m

That's still pretty big. Are you running a debug version of all libs (libc and such?) that would explain the size.

(both without mod_perl) but this resulted in a minimal gain once mod_perl was loaded.

How much added in numbers?