On Wed, Aug 05, 2020 at 10:47:48AM -0500, Mithun Bhattacharya wrote:
> Assuming that is genuine curiosity can we please not deviate from the topic
> ?
IBM felt that way once.
I think it is important to know what kind of aps we are developing, and
for what uses.. You are aware of the broad use
Assuming that is genuine curiosity can we please not deviate from the topic
?
On Wed, Aug 5, 2020 at 6:19 AM Ruben Safir wrote:
> On Wed, Aug 05, 2020 at 09:46:18AM +0800, Wesley Peng wrote:
> > Hi
> >
> > Mithun Bhattacharya wrote:
> > >Do you really need a webserver which is providing a
On 04.08.2020 22:48, Mark Blackman wrote:
[...]
the web server handles all the complicated host or path rewrites and access control and
the Perl app focuses on responding to the, now-sanitised, fully normalized, HTTP requests.
I'll agree to that, up to a point.
If you just want to write web
On Wed, Aug 05, 2020 at 09:46:18AM +0800, Wesley Peng wrote:
> Hi
>
> Mithun Bhattacharya wrote:
> >Do you really need a webserver which is providing a blocking service ?
>
> yes, this is a prediction server, which would be deployed in PROD
> environment, the client application would request the
>
>
> The good thing about Apache is it's dynamic rescaling - which isn't as easy
> with starman - if you have a large code base the spin up time for starman can
> be quite large as it appears (to make it efficient) load in every bit of code
> that the application needs - even if it is one
James,
James Smith wrote:
The services which use apache/mod_perl work reliably and return data for these
- the dancer/starman sometimes fail/hang as there are no backends to serve the
requests or those backends timeout requests to the nginx/proxy (but still
continue using resources). The
Wesley,
You will have seen my posts elsewhere - we work on large Terra/Peta byte scale
datasets {and these aren't a large number of large records but more a very,
very large number of small records} so the memory and response times are both
large - less so compute in some cases but not others.
