2011/7/22 Jiří Pavlovský :
> On 22.7.2011 18:15, Perrin Harkins wrote:
>>>
>>> However this doesn't work as Apache is segfaulting.
>>
>> That makes it sound like it is working but there's something in your
>> scripts that doesn't like being loaded in the parent process. Are you
>> opening up datab
I am not sure if this directly applies to your issue, but I got segfaults
in DBI when I just opened the DB handle once in the parent, reusing the
DBH in child processes (a bug). The issue went away when I ensured that
every child process did its own DBI->connect.
HTH
On 7/22/11 11:17 AM, "Jiří P
I have a MJPEG streaming system which uses mod_perl in the web
interface to supply the final stream to the client.
I am seeing high cpu utilization under RHEL5.6 which I don't see on
FC14. We are talking sub 10% on FC14 vs 80% on EL5. This is on
different hardware, but not that different. And on E
This may not be related, but when I was working with Centos 5 in a
Vmware environment, I ran into an issue of high cpu since the default
clock rate with Linux 2.6 is 1000Hz. I changed to a 100Hz clock rate
and got much lower cpu usage.
I'm not sure if that is your issue, perhaps FC14 was using le
Neither install is running within VMWare.
On Mon, Jul 25, 2011 at 5:55 PM, Fred Moyer wrote:
> This may not be related, but when I was working with Centos 5 in a
> Vmware environment, I ran into an issue of high cpu since the default
> clock rate with Linux 2.6 is 1000Hz. I changed to a 100Hz cl
On Mon, Jul 25, 2011 at 4:02 PM, Christopher Stanton
wrote:
> Neither install is running within VMWare.
Might be worthwhile trying a different rate though, or going tickless.
Perl 5.8.8 isn't that much (if at all) slower than 5.12. Looks like
the FC14 kernel is tickless:
http://docs.fedoraproj
Before I start playing mix-and-match with kernels, I would prefer some
feedback on mod_perl and the script's code.
It doesn't sleep in the main loop, but it should block on
my @ready = $select->can_read(1);
and not block on
if ( $sock->read(my $data, POSIX::BUFSIZ*10) ){
since the socket is set w
On Monday, 25 July 2011 23:31:04 McCarrell, Jeff wrote:
> I am not sure if this directly applies to your issue, but I got
> segfaults in DBI when I just opened the DB handle once in the parent,
> reusing the DBH in child processes (a bug). The issue went away when
> I ensured that every child proc
