> On 23 Dec 2020, at 11:36, James Smith wrote:
>
> Forgot to add - so our FCGI servers need a lot (and I mean a lot) more memory
> than the mod_perl servers to serve the same level of content (just in case
> memory blows up with FCGI backends)
>
I don’t believe this has to be true, I am pr
Preload of what doesnt work ?
On Fri, Jan 1, 2021 at 10:08 AM Ruben Safir wrote:
> >
> > This isn’t quite true - if you load modules before the process forks
> then they can cleverly share the same parts of memory. It is useful to be
> able to "pre-load" core functionality which is used across a
>
> This isn’t quite true - if you load modules before the process forks then
> they can cleverly share the same parts of memory. It is useful to be able to
> "pre-load" core functionality which is used across all functions {this is the
> case in Linux anyway}. It also speeds up child process g
he schema was set up – and then they realised it would take 12 months
>> to load the data
>> > which we had then (which is probably less than a millionth of what we
>> have now)!
>> >
>> > Moving compute off site is a problem as the transfer of the level of
&g
lem – you can’t easily move all the data to the compute – so
> you have to bring
> > the compute to the data.
> >
> > The site I worked on before I became a more general developer was doing
> that – and the
> > code that was written 12-15 years ago is actually still go
veloped as the scale of the data
has got so big that even the summary pages we produced 10 years ago have to be summarised
because they are so large.
*From:*Mithun Bhattacharya
*Sent:* 24 December 2020 00:06
*To:* mod_perl list
*Subject:* Re: Confused about two development utils [EXT]
James
che.org>>
Subject: Re: Confused about two development utils [EXT]
Today memory is not serious problem, each of our server has 64GB memory.
Forgot to add - so our FCGI servers need a lot (and I mean a lot) more memory
than the mod_perl servers to serve the same level of content (just in cas
to add - so our FCGI servers need a lot (and I mean a lot) more
> memory than the mod_perl servers to serve the same level of content (just
> in case memory blows up with FCGI backends)
>
> -Original Message-
> From: James Smith
> Sent: 23 December 2020 11:34
> To: André Warnier (tom
strain than in other areas of
the world – it is just that we know we have because of the amount of sequencing
and analysis that we in the UK have done.
From: Matthias Peng
Sent: 23 December 2020 12:02
To: mod_perl list
Subject: Re: Confused about two development utils [EXT]
Today memory is not
unsubscribe.
On Wed, Dec 23, 2020 at 5:05 PM James Smith wrote:
>
> > This costs memory, and all the more since many perl modules are not
> thread-safe, so if you use them in your code, at this moment the only safe
> way to do it is to use the Apache httpd prefork model. This means that each
> A
riginal Message-
> From: James Smith
> Sent: 23 December 2020 11:34
> To: André Warnier (tomcat/perl) ; modperl@perl.apache.org
> Subject: RE: Confused about two development utils [EXT]
>
>
> > This costs memory, and all the more since many perl modules are not
> thread
) ; modperl@perl.apache.org
Subject: RE: Confused about two development utils [EXT]
> This costs memory, and all the more since many perl modules are not
> thread-safe, so if you use them in your code, at this moment the only safe
> way to do it is to use the Apache httpd prefork mo
> This costs memory, and all the more since many perl modules are not
> thread-safe, so if you use them in your code, at this moment the only safe
> way to do it is to use the Apache httpd prefork model. This means that each
> Apache httpd child process has its own copy of the perl interpreter,
13 matches
Mail list logo
