You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl@perl.apache.org by Vincent Veyron <vv...@wanadoo.fr> on 2021/02/07 19:05:39 UTC
Re: Moving ExecCGI to mod_perl - performance and custom 'modules'
[EXT]
On Sun, 07 Feb 2021 23:58:17 +1100
Steven Haigh <ne...@crc.id.au> wrote:
>
> I haven't gotten into the preload or DBI sharing yet - as that'll end
> up needing a bit of a rewrite of code to take advantage of. I'd be open
> to suggestions here from those who have done it in the past to save me
> going down some dead ends :D
I use mod_perl handlers, so not sure how it mixes with PerlRegistry, but you probably want to have a look at connect_cached
--
Bien à vous, Vincent Veyron
https://compta.libremen.com
Logiciel libre de comptabilité générale en partie double
RE: Moving ExecCGI to mod_perl - performance and custom 'modules'
[EXT]
Posted by James Smith <js...@sanger.ac.uk>.
The advantage of the web proxy is not from securing your app - although there are things you can do on the reverse proxy to secure less secure apps
It's main advantage is that it doesn't run a large software stack - and so it makes it harder for people to compromise your front end and then compromise your internal networks, and even then they have to get from that DMZ into your main infrastructure.
We go a step further at work. We have a DMZ <- a web zone <- internal zone - so even if you can compromise the DMZ and the web servers you still don't have direct access to the other machines - taking servers + desktop machines - something like 30-50K cores.
-----Original Message-----
From: Clive Eisen <cl...@hildebrand.co.uk>
Sent: 09 February 2021 19:23
To: Rafael Caceres <rc...@aasa.com.pe>
Cc: James Smith <js...@sanger.ac.uk>; Vincent Veyron <vv...@wanadoo.fr>; modperl@perl.apache.org
Subject: Re: Moving ExecCGI to mod_perl - performance and custom 'modules' [EXT]
> On 9 Feb 2021, at 19:16, Rafael Caceres <rc...@aasa.com.pe> wrote:
>
> Another thing that can be done is keep the app server + DB inside your LAN and place a reverse proxy on your DMZ, that adds some level of protection.
Not really - the only protection is if all your apis or web pages are secure - the reverse proxy does not help or hinder that.
—
C
--
The Wellcome Sanger Institute is operated by Genome Research
Limited, a charity registered in England with number 1021457 and a
company registered in England with number 2742969, whose registered
office is 215 Euston Road, London, NW1 2BE.
Re: Moving ExecCGI to mod_perl - performance and custom 'modules'
[EXT]
Posted by Clive Eisen <cl...@hildebrand.co.uk>.
> On 9 Feb 2021, at 19:16, Rafael Caceres <rc...@aasa.com.pe> wrote:
>
> Another thing that can be done is keep the app server + DB inside your LAN and place a reverse proxy on your DMZ, that adds some level of protection.
Not really - the only protection is if all your apis or web pages are secure - the reverse proxy does not help or hinder that.
—
C
Re: Moving ExecCGI to mod_perl - performance and custom 'modules'
[EXT]
Posted by Rafael Caceres <rc...@aasa.com.pe>.
Another thing that can be done is keep the app server + DB inside your LAN and place a reverse proxy on your DMZ, that adds some level of protection.
Rafael
On Feb 9, 2021, 2:08 PM -0500, Clive Eisen <cl...@hildebrand.co.uk>, wrote:
On 9 Feb 2021, at 18:45, James Smith <js...@sanger.ac.uk> wrote:
It doesn't matter what db - and whether you wrap it in eval it is a problem (postgres has a similar problem - the one with least problems is MySQL) - if you have a secure environment where your databases are in a firewalled zone it will happen to all of them... It's a nasty bit of networking - it does mean our meant to be secure enterprise level apps running against Oracle and less secure and less stable than the other apps we have (go figure!)…
20 years ago I had exactly this argument with Amex when we wanted to use it for payment on the site I then worked for.
They said put a firewall between the app and db layerx
I said it's a dedicated nic/vlan on both sides and the ONLY port that is open is the db - what is a firewall going to add to that.
Eventually they agreed.
Security people who say firewall firewall firewall will solve all your security issues (or even some of them) are useless.
Most of them do it by the book - which should in all case just be the starting point.
Just my 2p
—
C
Re: Moving ExecCGI to mod_perl - performance and custom 'modules'
[EXT]
Posted by Clive Eisen <cl...@hildebrand.co.uk>.
> On 9 Feb 2021, at 18:45, James Smith <js...@sanger.ac.uk> wrote:
>
> It doesn't matter what db - and whether you wrap it in eval it is a problem (postgres has a similar problem - the one with least problems is MySQL) - if you have a secure environment where your databases are in a firewalled zone it will happen to all of them... It's a nasty bit of networking - it does mean our meant to be secure enterprise level apps running against Oracle and less secure and less stable than the other apps we have (go figure!)…
20 years ago I had exactly this argument with Amex when we wanted to use it for payment on the site I then worked for.
They said put a firewall between the app and db layerx
I said it's a dedicated nic/vlan on both sides and the ONLY port that is open is the db - what is a firewall going to add to that.
Eventually they agreed.
Security people who say firewall firewall firewall will solve all your security issues (or even some of them) are useless.
Most of them do it by the book - which should in all case just be the starting point.
Just my 2p
—
C
RE: Moving ExecCGI to mod_perl - performance and custom 'modules'
[EXT]
Posted by James Smith <js...@sanger.ac.uk>.
It doesn't matter what db - and whether you wrap it in eval it is a problem (postgres has a similar problem - the one with least problems is MySQL) - if you have a secure environment where your databases are in a firewalled zone it will happen to all of them... It's a nasty bit of networking - it does mean our meant to be secure enterprise level apps running against Oracle and less secure and less stable than the other apps we have (go figure!)...
-----Original Message-----
From: Vincent Veyron <vv...@wanadoo.fr>
Sent: 09 February 2021 17:47
To: modperl@perl.apache.org
Subject: Re: Moving ExecCGI to mod_perl - performance and custom 'modules' [EXT]
On Sun, 7 Feb 2021 20:21:34 +0000
James Smith <js...@sanger.ac.uk> wrote:
Hi James,
> DBI sharing doesn't really gain you much - and can actually lead you into a whole world of pain. It isn't actually worth turning it on at all.
>
Never had a problem with it myself in years of using it, but I wrap my queries in an eval { } and check $@, so that the scripts are not left hanging; also I have a postgresql db ;-).
I ran some tests with ab, I do see an improvement in response speed :
my $dbh = DBI->connect()
Concurrency Level: 5
Time taken for tests: 22.198 seconds
Complete requests: 1000
Failed requests: 0
Total transferred: 8435000 bytes
HTML transferred: 8176000 bytes
Requests per second: 45.05 [#/sec] (mean)
Time per request: 110.990 [ms] (mean)
Time per request: 22.198 [ms] (mean, across all concurrent requests)
Transfer rate: 371.08 [Kbytes/sec] received
my $dbh = DBI->connect_cached()
Concurrency Level: 5
Time taken for tests: 15.133 seconds
Complete requests: 1000
Failed requests: 0
Total transferred: 8435000 bytes
HTML transferred: 8176000 bytes
Requests per second: 66.08 [#/sec] (mean)
Time per request: 75.664 [ms] (mean)
Time per request: 15.133 [ms] (mean, across all concurrent requests)
Transfer rate: 544.33 [Kbytes/sec] received
--
Bien à vous, Vincent Veyron
https://urldefense.proofpoint.com/v2/url?u=https-3A__compta.libremen.com&d=DwIFAw&c=D7ByGjS34AllFgecYw0iC6Zq7qlm8uclZFI0SqQnqBo&r=oH2yp0ge1ecj4oDX0XM7vQ&m=u0vYr2KXDAvFiif8YsX-7Uho_gsySe2x9Z3OHcD_Br4&s=7Hyp0l39Edk8cAZK0idIxVxKi3OQXhkR96T0T42b2tM&e=
Logiciel libre de comptabilité générale en partie double
--
The Wellcome Sanger Institute is operated by Genome Research
Limited, a charity registered in England with number 1021457 and a
company registered in England with number 2742969, whose registered
office is 215 Euston Road, London, NW1 2BE.
Re: Moving ExecCGI to mod_perl - performance and custom 'modules'
[EXT]
Posted by Chris <cp...@bennettconstruction.us>.
On Fri, Feb 12, 2021 at 05:15:29PM +0100, André Warnier (tomcat/perl) wrote:
> My comment was just basically so as to avoid the case where someone else
> would later be searching the archives of this mailing list for information
> about DBI, and never find these (useful for DBI) posts, because DBI is not
> in the subject.
I can't disagree with that. Put up a short thread for the archives with a good
subject and content about what this thread references with some kind of link
to this thread?
Some of the good topics I really found helpful are also long threads
that wander around getting off-topic of the subject. I've saved quite a
few useful posts from those threads. Good archiving is very important.
I have found using regular web search engines to be an exercise in
useless frustration.
I'm reading up on several of the topics here. I plan to ask some more
questions about those after a bit. What is a good way to reference back
to this thread's sections that will get into the archive in a useful way?
Chris
>
> On 12.02.2021 00:51, Chris wrote:
> > On Thu, Feb 11, 2021 at 09:52:16AM +0100, André Warnier (tomcat/perl) wrote:
> > > Isn't this discussion about connection pools and firewalls etc getting a bit
> > > far from the initial subject of the thread ?
> >
> > Perhaps. But this has become a pretty low volume mailing list.
> > This "thread" has moved me to spend hours looking at changing and/or
> > better understanding the work I have done (pretty old code) and the
> > work I am now starting.
> >
> > For me, I'm re-reading the manual pages for the DBI modules,
> > etc. I've also added another mailing list to follow about DBI.
> >
> > And I will now have some threads to add in the near future.
> > Threads I wouldn't have thought of.
> > But this isn't my mailing list, so breaking these topics into new
> > threads is just fine. Not a problem at all. 8-)
> >
> > Recently, something "clicked on" for me about mod_perl.
> > Which is pretty thrilling for me. ;-}
> >
> > Chris
> >
> >
> > >
> > > On 09.02.2021 23:03, Mithun Bhattacharya wrote:
> > > > I would consider mine a small setup on an internal network and I have
> > > > used both Sybase and SQL Server. In our case the DBA's preferred us to
> > > > remain connected rather than make too many connections - we need DB
> > > > access in bursts - it could be quiet for more than an hour and then
> > > > suddenly we might need hundreds of connections within few minutes (if we
> > > > didnt cache it). Another thing was we were connecting from forked
> > > > processes so at some point everything gets reaped including the
> > > > connections. Our style of coding has been to connect to the DB wherever
> > > > we actually need to fire one or more SQLs and do connect_cached in the
> > > > actual implementation (it is a separate library since we had to place a
> > > > wrapper to acquire credentials)
> > > >
> > > > On Tue, Feb 9, 2021 at 2:34 PM James Smith <js5@sanger.ac.uk <ma...@sanger.ac.uk>> wrote:
> > > >
> > > > Mithun,
> > > >
> > > > I’m not sure on what scale you work – but these are from experience in sites with
> > > > small to medium load – and we rarely see an appreciable gain in using cached or pooled
> > > > connections, just the occasional heartache they cause.
> > > > If you are working on small applications with a minimal number of databases on the DB
> > > > server then you may see some performance improvement (but tbh not as much as you used
> > > > to – as the servers have changed) Unfortunately I don’t in both my main and secondary
> > > > roles, and I know many others who come across these limitations as well.
> > > >
> > > > I’m not saying don’t use persistent or cached connections – but leaving it to some
> > > > hidden layers is not necessarily a good thing to do – it can have unforeseen side
> > > > effects {and Apache::DBI & PHP pconnect have both shown these up}
> > > >
> > > > If you are working with e.g. with MySQL the overhead of the (socket) connection is
> > > > very small, but having more connections open to cope with persistent connections
> > > > {memory wise} often needs specifying a much large database server – or not being able
> > > > to do all the nice tricks to in memory indexes and queries [to increase query
> > > > performance]. Being able to chose which connections you keep open and which you
> > > > open/close on a per request basis gives you the benefits of caching without the risks
> > > > involved [other than the “lock table” issue].____
> > > >
> > > > __ __
> > > >
> > > > __ __
> > > >
> > > > *From:*Mithun Bhattacharya <mithnb@gmail.com <ma...@gmail.com>>
> > > > *Sent:* 09 February 2021 18:34
> > > > *To:* mod_perl list <modperl@perl.apache.org <ma...@perl.apache.org>>
> > > > *Subject:* Re: Moving ExecCGI to mod_perl - performance and custom 'modules' [EXT]____
> > > >
> > > > __ __
> > > >
> > > > Connection caching does work for most use cases - we have to accept James works in
> > > > scenarios most developers can't fathom :) ____
> > > >
> > > > __ __
> > > >
> > > > If you are just firing off simple SQL's without any triggers or named temporary tables
> > > > involved you should be good. The only times we recall tripping on cached connection is
> > > > when two different code snippets tried to create the same temporary table. Another
> > > > time the code was expecting the disconnect to complete the connection cleanup.____
> > > >
> > > > __ __
> > > >
> > > > On Tue, Feb 9, 2021 at 11:47 AM Vincent Veyron <vv.lists@wanadoo.fr
> > > > <ma...@wanadoo.fr>> wrote:____
> > > >
> > > > On Sun, 7 Feb 2021 20:21:34 +0000
> > > > James Smith <js5@sanger.ac.uk <ma...@sanger.ac.uk>> wrote:
> > > >
> > > > Hi James,
> > > >
> > > > > DBI sharing doesn't really gain you much - and can actually lead you into a
> > > > whole world of pain. It isn't actually worth turning it on at all.
> > > > >
> > > >
> > > > Never had a problem with it myself in years of using it, but I wrap my queries in
> > > > an eval { } and check $@, so that the scripts are not left hanging; also I have a
> > > > postgresql db ;-).
> > > >
> > > > I ran some tests with ab, I do see an improvement in response speed :
> > > >
> > > > my $dbh = DBI->connect()
> > > > Concurrency Level: 5
> > > > Time taken for tests: 22.198 seconds
> > > > Complete requests: 1000
> > > > Failed requests: 0
> > > > Total transferred: 8435000 bytes
> > > > HTML transferred: 8176000 bytes
> > > > Requests per second: 45.05 [#/sec] (mean)
> > > > Time per request: 110.990 [ms] (mean)
> > > > Time per request: 22.198 [ms] (mean, across all concurrent requests)
> > > > Transfer rate: 371.08 [Kbytes/sec] received
> > > >
> > > > my $dbh = DBI->connect_cached()
> > > > Concurrency Level: 5
> > > > Time taken for tests: 15.133 seconds
> > > > Complete requests: 1000
> > > > Failed requests: 0
> > > > Total transferred: 8435000 bytes
> > > > HTML transferred: 8176000 bytes
> > > > Requests per second: 66.08 [#/sec] (mean)
> > > > Time per request: 75.664 [ms] (mean)
> > > > Time per request: 15.133 [ms] (mean, across all concurrent requests)
> > > > Transfer rate: 544.33 [Kbytes/sec] received
> > > >
> > > >
> > > > --
> > > >
> > > > Bien à vous, Vincent Veyron
> > > >
> > > > https://compta.libremen.com [compta.libremen.com]
> > > > <https://urldefense.proofpoint.com/v2/url?u=https-3A__compta.libremen.com&d=DwMFaQ&c=D7ByGjS34AllFgecYw0iC6Zq7qlm8uclZFI0SqQnqBo&r=oH2yp0ge1ecj4oDX0XM7vQ&m=CnIW-j3Bw_IfohZCciiwtkoqvr6nV2hHrNYMPpEOe8E&s=uf6Qi4tnTPryVuPvOKwfZQcFOksecWyn-LYPDVj44lY&e=>
> > > > Logiciel libre de comptabilité générale en partie double
> > > >
> > > >
> > > > ____
> > > >
> > > > -- The Wellcome Sanger Institute is operated by Genome Research Limited, a charity
> > > > registered in England with number 1021457 and a company registered in England with
> > > > number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE.
> > > >
> > >
>
Re: Moving ExecCGI to mod_perl - performance and custom 'modules'
[EXT]
Posted by "André Warnier (tomcat/perl)" <aw...@ice-sa.com>.
My comment was just basically so as to avoid the case where someone else would later be
searching the archives of this mailing list for information about DBI, and never find
these (useful for DBI) posts, because DBI is not in the subject.
On 12.02.2021 00:51, Chris wrote:
> On Thu, Feb 11, 2021 at 09:52:16AM +0100, André Warnier (tomcat/perl) wrote:
>> Isn't this discussion about connection pools and firewalls etc getting a bit
>> far from the initial subject of the thread ?
>
> Perhaps. But this has become a pretty low volume mailing list.
> This "thread" has moved me to spend hours looking at changing and/or
> better understanding the work I have done (pretty old code) and the
> work I am now starting.
>
> For me, I'm re-reading the manual pages for the DBI modules,
> etc. I've also added another mailing list to follow about DBI.
>
> And I will now have some threads to add in the near future.
> Threads I wouldn't have thought of.
> But this isn't my mailing list, so breaking these topics into new
> threads is just fine. Not a problem at all. 8-)
>
> Recently, something "clicked on" for me about mod_perl.
> Which is pretty thrilling for me. ;-}
>
> Chris
>
>
>>
>> On 09.02.2021 23:03, Mithun Bhattacharya wrote:
>>> I would consider mine a small setup on an internal network and I have
>>> used both Sybase and SQL Server. In our case the DBA's preferred us to
>>> remain connected rather than make too many connections - we need DB
>>> access in bursts - it could be quiet for more than an hour and then
>>> suddenly we might need hundreds of connections within few minutes (if we
>>> didnt cache it). Another thing was we were connecting from forked
>>> processes so at some point everything gets reaped including the
>>> connections. Our style of coding has been to connect to the DB wherever
>>> we actually need to fire one or more SQLs and do connect_cached in the
>>> actual implementation (it is a separate library since we had to place a
>>> wrapper to acquire credentials)
>>>
>>> On Tue, Feb 9, 2021 at 2:34 PM James Smith <js5@sanger.ac.uk <ma...@sanger.ac.uk>> wrote:
>>>
>>> Mithun,
>>>
>>> I’m not sure on what scale you work – but these are from experience in sites with
>>> small to medium load – and we rarely see an appreciable gain in using cached or pooled
>>> connections, just the occasional heartache they cause.
>>> If you are working on small applications with a minimal number of databases on the DB
>>> server then you may see some performance improvement (but tbh not as much as you used
>>> to – as the servers have changed) Unfortunately I don’t in both my main and secondary
>>> roles, and I know many others who come across these limitations as well.
>>>
>>> I’m not saying don’t use persistent or cached connections – but leaving it to some
>>> hidden layers is not necessarily a good thing to do – it can have unforeseen side
>>> effects {and Apache::DBI & PHP pconnect have both shown these up}
>>>
>>> If you are working with e.g. with MySQL the overhead of the (socket) connection is
>>> very small, but having more connections open to cope with persistent connections
>>> {memory wise} often needs specifying a much large database server – or not being able
>>> to do all the nice tricks to in memory indexes and queries [to increase query
>>> performance]. Being able to chose which connections you keep open and which you
>>> open/close on a per request basis gives you the benefits of caching without the risks
>>> involved [other than the “lock table” issue].____
>>>
>>> __ __
>>>
>>> __ __
>>>
>>> *From:*Mithun Bhattacharya <mithnb@gmail.com <ma...@gmail.com>>
>>> *Sent:* 09 February 2021 18:34
>>> *To:* mod_perl list <modperl@perl.apache.org <ma...@perl.apache.org>>
>>> *Subject:* Re: Moving ExecCGI to mod_perl - performance and custom 'modules' [EXT]____
>>>
>>> __ __
>>>
>>> Connection caching does work for most use cases - we have to accept James works in
>>> scenarios most developers can't fathom :) ____
>>>
>>> __ __
>>>
>>> If you are just firing off simple SQL's without any triggers or named temporary tables
>>> involved you should be good. The only times we recall tripping on cached connection is
>>> when two different code snippets tried to create the same temporary table. Another
>>> time the code was expecting the disconnect to complete the connection cleanup.____
>>>
>>> __ __
>>>
>>> On Tue, Feb 9, 2021 at 11:47 AM Vincent Veyron <vv.lists@wanadoo.fr
>>> <ma...@wanadoo.fr>> wrote:____
>>>
>>> On Sun, 7 Feb 2021 20:21:34 +0000
>>> James Smith <js5@sanger.ac.uk <ma...@sanger.ac.uk>> wrote:
>>>
>>> Hi James,
>>>
>>> > DBI sharing doesn't really gain you much - and can actually lead you into a
>>> whole world of pain. It isn't actually worth turning it on at all.
>>> >
>>>
>>> Never had a problem with it myself in years of using it, but I wrap my queries in
>>> an eval { } and check $@, so that the scripts are not left hanging; also I have a
>>> postgresql db ;-).
>>>
>>> I ran some tests with ab, I do see an improvement in response speed :
>>>
>>> my $dbh = DBI->connect()
>>> Concurrency Level: 5
>>> Time taken for tests: 22.198 seconds
>>> Complete requests: 1000
>>> Failed requests: 0
>>> Total transferred: 8435000 bytes
>>> HTML transferred: 8176000 bytes
>>> Requests per second: 45.05 [#/sec] (mean)
>>> Time per request: 110.990 [ms] (mean)
>>> Time per request: 22.198 [ms] (mean, across all concurrent requests)
>>> Transfer rate: 371.08 [Kbytes/sec] received
>>>
>>> my $dbh = DBI->connect_cached()
>>> Concurrency Level: 5
>>> Time taken for tests: 15.133 seconds
>>> Complete requests: 1000
>>> Failed requests: 0
>>> Total transferred: 8435000 bytes
>>> HTML transferred: 8176000 bytes
>>> Requests per second: 66.08 [#/sec] (mean)
>>> Time per request: 75.664 [ms] (mean)
>>> Time per request: 15.133 [ms] (mean, across all concurrent requests)
>>> Transfer rate: 544.33 [Kbytes/sec] received
>>>
>>>
>>> --
>>>
>>> Bien à vous, Vincent Veyron
>>>
>>> https://compta.libremen.com [compta.libremen.com]
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__compta.libremen.com&d=DwMFaQ&c=D7ByGjS34AllFgecYw0iC6Zq7qlm8uclZFI0SqQnqBo&r=oH2yp0ge1ecj4oDX0XM7vQ&m=CnIW-j3Bw_IfohZCciiwtkoqvr6nV2hHrNYMPpEOe8E&s=uf6Qi4tnTPryVuPvOKwfZQcFOksecWyn-LYPDVj44lY&e=>
>>> Logiciel libre de comptabilité générale en partie double
>>>
>>>
>>> ____
>>>
>>> -- The Wellcome Sanger Institute is operated by Genome Research Limited, a charity
>>> registered in England with number 1021457 and a company registered in England with
>>> number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE.
>>>
>>
Re: Moving ExecCGI to mod_perl - performance and custom 'modules'
[EXT]
Posted by Chris <cp...@bennettconstruction.us>.
On Thu, Feb 11, 2021 at 09:52:16AM +0100, André Warnier (tomcat/perl) wrote:
> Isn't this discussion about connection pools and firewalls etc getting a bit
> far from the initial subject of the thread ?
Perhaps. But this has become a pretty low volume mailing list.
This "thread" has moved me to spend hours looking at changing and/or
better understanding the work I have done (pretty old code) and the
work I am now starting.
For me, I'm re-reading the manual pages for the DBI modules,
etc. I've also added another mailing list to follow about DBI.
And I will now have some threads to add in the near future.
Threads I wouldn't have thought of.
But this isn't my mailing list, so breaking these topics into new
threads is just fine. Not a problem at all. 8-)
Recently, something "clicked on" for me about mod_perl.
Which is pretty thrilling for me. ;-}
Chris
>
> On 09.02.2021 23:03, Mithun Bhattacharya wrote:
> > I would consider mine a small setup on an internal network and I have
> > used both Sybase and SQL Server. In our case the DBA's preferred us to
> > remain connected rather than make too many connections - we need DB
> > access in bursts - it could be quiet for more than an hour and then
> > suddenly we might need hundreds of connections within few minutes (if we
> > didnt cache it). Another thing was we were connecting from forked
> > processes so at some point everything gets reaped including the
> > connections. Our style of coding has been to connect to the DB wherever
> > we actually need to fire one or more SQLs and do connect_cached in the
> > actual implementation (it is a separate library since we had to place a
> > wrapper to acquire credentials)
> >
> > On Tue, Feb 9, 2021 at 2:34 PM James Smith <js5@sanger.ac.uk <ma...@sanger.ac.uk>> wrote:
> >
> > Mithun,
> >
> > I’m not sure on what scale you work – but these are from experience in sites with
> > small to medium load – and we rarely see an appreciable gain in using cached or pooled
> > connections, just the occasional heartache they cause.
> > If you are working on small applications with a minimal number of databases on the DB
> > server then you may see some performance improvement (but tbh not as much as you used
> > to – as the servers have changed) Unfortunately I don’t in both my main and secondary
> > roles, and I know many others who come across these limitations as well.
> >
> > I’m not saying don’t use persistent or cached connections – but leaving it to some
> > hidden layers is not necessarily a good thing to do – it can have unforeseen side
> > effects {and Apache::DBI & PHP pconnect have both shown these up}
> >
> > If you are working with e.g. with MySQL the overhead of the (socket) connection is
> > very small, but having more connections open to cope with persistent connections
> > {memory wise} often needs specifying a much large database server – or not being able
> > to do all the nice tricks to in memory indexes and queries [to increase query
> > performance]. Being able to chose which connections you keep open and which you
> > open/close on a per request basis gives you the benefits of caching without the risks
> > involved [other than the “lock table” issue].____
> >
> > __ __
> >
> > __ __
> >
> > *From:*Mithun Bhattacharya <mithnb@gmail.com <ma...@gmail.com>>
> > *Sent:* 09 February 2021 18:34
> > *To:* mod_perl list <modperl@perl.apache.org <ma...@perl.apache.org>>
> > *Subject:* Re: Moving ExecCGI to mod_perl - performance and custom 'modules' [EXT]____
> >
> > __ __
> >
> > Connection caching does work for most use cases - we have to accept James works in
> > scenarios most developers can't fathom :) ____
> >
> > __ __
> >
> > If you are just firing off simple SQL's without any triggers or named temporary tables
> > involved you should be good. The only times we recall tripping on cached connection is
> > when two different code snippets tried to create the same temporary table. Another
> > time the code was expecting the disconnect to complete the connection cleanup.____
> >
> > __ __
> >
> > On Tue, Feb 9, 2021 at 11:47 AM Vincent Veyron <vv.lists@wanadoo.fr
> > <ma...@wanadoo.fr>> wrote:____
> >
> > On Sun, 7 Feb 2021 20:21:34 +0000
> > James Smith <js5@sanger.ac.uk <ma...@sanger.ac.uk>> wrote:
> >
> > Hi James,
> >
> > > DBI sharing doesn't really gain you much - and can actually lead you into a
> > whole world of pain. It isn't actually worth turning it on at all.
> > >
> >
> > Never had a problem with it myself in years of using it, but I wrap my queries in
> > an eval { } and check $@, so that the scripts are not left hanging; also I have a
> > postgresql db ;-).
> >
> > I ran some tests with ab, I do see an improvement in response speed :
> >
> > my $dbh = DBI->connect()
> > Concurrency Level: 5
> > Time taken for tests: 22.198 seconds
> > Complete requests: 1000
> > Failed requests: 0
> > Total transferred: 8435000 bytes
> > HTML transferred: 8176000 bytes
> > Requests per second: 45.05 [#/sec] (mean)
> > Time per request: 110.990 [ms] (mean)
> > Time per request: 22.198 [ms] (mean, across all concurrent requests)
> > Transfer rate: 371.08 [Kbytes/sec] received
> >
> > my $dbh = DBI->connect_cached()
> > Concurrency Level: 5
> > Time taken for tests: 15.133 seconds
> > Complete requests: 1000
> > Failed requests: 0
> > Total transferred: 8435000 bytes
> > HTML transferred: 8176000 bytes
> > Requests per second: 66.08 [#/sec] (mean)
> > Time per request: 75.664 [ms] (mean)
> > Time per request: 15.133 [ms] (mean, across all concurrent requests)
> > Transfer rate: 544.33 [Kbytes/sec] received
> >
> >
> > --
> >
> > Bien à vous, Vincent Veyron
> >
> > https://compta.libremen.com [compta.libremen.com]
> > <https://urldefense.proofpoint.com/v2/url?u=https-3A__compta.libremen.com&d=DwMFaQ&c=D7ByGjS34AllFgecYw0iC6Zq7qlm8uclZFI0SqQnqBo&r=oH2yp0ge1ecj4oDX0XM7vQ&m=CnIW-j3Bw_IfohZCciiwtkoqvr6nV2hHrNYMPpEOe8E&s=uf6Qi4tnTPryVuPvOKwfZQcFOksecWyn-LYPDVj44lY&e=>
> > Logiciel libre de comptabilité générale en partie double
> >
> >
> > ____
> >
> > -- The Wellcome Sanger Institute is operated by Genome Research Limited, a charity
> > registered in England with number 1021457 and a company registered in England with
> > number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE.
> >
>
Re: Moving ExecCGI to mod_perl - performance and custom 'modules'
[EXT]
Posted by "André Warnier (tomcat/perl)" <aw...@ice-sa.com>.
Isn't this discussion about connection pools and firewalls etc getting a bit far from the
initial subject of the thread ?
On 09.02.2021 23:03, Mithun Bhattacharya wrote:
> I would consider mine a small setup on an internal network and I have used both Sybase and
> SQL Server. In our case the DBA's preferred us to remain connected rather than make too
> many connections - we need DB access in bursts - it could be quiet for more than an hour
> and then suddenly we might need hundreds of connections within few minutes (if we didnt
> cache it). Another thing was we were connecting from forked processes so at some point
> everything gets reaped including the connections. Our style of coding has been to connect
> to the DB wherever we actually need to fire one or more SQLs and do connect_cached in the
> actual implementation (it is a separate library since we had to place a wrapper to
> acquire credentials)
>
> On Tue, Feb 9, 2021 at 2:34 PM James Smith <js5@sanger.ac.uk <ma...@sanger.ac.uk>> wrote:
>
> Mithun,
>
> I’m not sure on what scale you work – but these are from experience in sites with
> small to medium load – and we rarely see an appreciable gain in using cached or pooled
> connections, just the occasional heartache they cause.
> If you are working on small applications with a minimal number of databases on the DB
> server then you may see some performance improvement (but tbh not as much as you used
> to – as the servers have changed) Unfortunately I don’t in both my main and secondary
> roles, and I know many others who come across these limitations as well.
>
> I’m not saying don’t use persistent or cached connections – but leaving it to some
> hidden layers is not necessarily a good thing to do – it can have unforeseen side
> effects {and Apache::DBI & PHP pconnect have both shown these up}
>
> If you are working with e.g. with MySQL the overhead of the (socket) connection is
> very small, but having more connections open to cope with persistent connections
> {memory wise} often needs specifying a much large database server – or not being able
> to do all the nice tricks to in memory indexes and queries [to increase query
> performance]. Being able to chose which connections you keep open and which you
> open/close on a per request basis gives you the benefits of caching without the risks
> involved [other than the “lock table” issue].____
>
> __ __
>
> __ __
>
> *From:*Mithun Bhattacharya <mithnb@gmail.com <ma...@gmail.com>>
> *Sent:* 09 February 2021 18:34
> *To:* mod_perl list <modperl@perl.apache.org <ma...@perl.apache.org>>
> *Subject:* Re: Moving ExecCGI to mod_perl - performance and custom 'modules' [EXT]____
>
> __ __
>
> Connection caching does work for most use cases - we have to accept James works in
> scenarios most developers can't fathom :) ____
>
> __ __
>
> If you are just firing off simple SQL's without any triggers or named temporary tables
> involved you should be good. The only times we recall tripping on cached connection is
> when two different code snippets tried to create the same temporary table. Another
> time the code was expecting the disconnect to complete the connection cleanup.____
>
> __ __
>
> On Tue, Feb 9, 2021 at 11:47 AM Vincent Veyron <vv.lists@wanadoo.fr
> <ma...@wanadoo.fr>> wrote:____
>
> On Sun, 7 Feb 2021 20:21:34 +0000
> James Smith <js5@sanger.ac.uk <ma...@sanger.ac.uk>> wrote:
>
> Hi James,
>
> > DBI sharing doesn't really gain you much - and can actually lead you into a
> whole world of pain. It isn't actually worth turning it on at all.
> >
>
> Never had a problem with it myself in years of using it, but I wrap my queries in
> an eval { } and check $@, so that the scripts are not left hanging; also I have a
> postgresql db ;-).
>
> I ran some tests with ab, I do see an improvement in response speed :
>
> my $dbh = DBI->connect()
> Concurrency Level: 5
> Time taken for tests: 22.198 seconds
> Complete requests: 1000
> Failed requests: 0
> Total transferred: 8435000 bytes
> HTML transferred: 8176000 bytes
> Requests per second: 45.05 [#/sec] (mean)
> Time per request: 110.990 [ms] (mean)
> Time per request: 22.198 [ms] (mean, across all concurrent requests)
> Transfer rate: 371.08 [Kbytes/sec] received
>
> my $dbh = DBI->connect_cached()
> Concurrency Level: 5
> Time taken for tests: 15.133 seconds
> Complete requests: 1000
> Failed requests: 0
> Total transferred: 8435000 bytes
> HTML transferred: 8176000 bytes
> Requests per second: 66.08 [#/sec] (mean)
> Time per request: 75.664 [ms] (mean)
> Time per request: 15.133 [ms] (mean, across all concurrent requests)
> Transfer rate: 544.33 [Kbytes/sec] received
>
>
> --
>
> Bien à vous, Vincent Veyron
>
> https://compta.libremen.com [compta.libremen.com]
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__compta.libremen.com&d=DwMFaQ&c=D7ByGjS34AllFgecYw0iC6Zq7qlm8uclZFI0SqQnqBo&r=oH2yp0ge1ecj4oDX0XM7vQ&m=CnIW-j3Bw_IfohZCciiwtkoqvr6nV2hHrNYMPpEOe8E&s=uf6Qi4tnTPryVuPvOKwfZQcFOksecWyn-LYPDVj44lY&e=>
> Logiciel libre de comptabilité générale en partie double
>
>
> ____
>
> -- The Wellcome Sanger Institute is operated by Genome Research Limited, a charity
> registered in England with number 1021457 and a company registered in England with
> number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE.
>
Re: Moving ExecCGI to mod_perl - performance and custom 'modules'
[EXT]
Posted by Dave Morgan <da...@1001111.com>.
As a long time Oracle DBA and perl mangler I have refrained from joining
this conversation until now.
Connection caching is a configuration option in DBI, not a coding
requirement. For web servers it is a single line edit in startup.pl
import DBICache versus import DBI if I recall incorrectly.
NO CODE CHANGES REQUIRED
Now caching connections will require clean code. Code that was
acceptable on a short term connection
causes problems on long term connections. Cursors left open, virtual
connections not closed, etc
are non-issues using DBI but huge problems with DBICache
Applications doing heavy sql or batch work should not use DBICache. Just
from an administrative perspective.
Session less applications like web servers SHALL use it. And I use the
legal meaning for shall
I don't care what database is on the end of a DBI connection, I mangle
em all, poorly
YMMV
Dave
--
Dave Morgan
Senior Consultant, 1001111 Alberta Limited
dave.morgan@1001111.com
403 399 2442
Re: Moving ExecCGI to mod_perl - performance and custom 'modules' [EXT]
Posted by Mithun Bhattacharya <mi...@gmail.com>.
I would consider mine a small setup on an internal network and I have used
both Sybase and SQL Server. In our case the DBA's preferred us to remain
connected rather than make too many connections - we need DB access in
bursts - it could be quiet for more than an hour and then suddenly we might
need hundreds of connections within few minutes (if we didnt cache it).
Another thing was we were connecting from forked processes so at some point
everything gets reaped including the connections. Our style of coding has
been to connect to the DB wherever we actually need to fire one or more
SQLs and do connect_cached in the actual implementation (it is a separate
library since we had to place a wrapper to acquire credentials)
On Tue, Feb 9, 2021 at 2:34 PM James Smith <js...@sanger.ac.uk> wrote:
> Mithun,
>
> I’m not sure on what scale you work – but these are from experience in
> sites with small to medium load – and we rarely see an appreciable gain in
> using cached or pooled connections, just the occasional heartache they
> cause.
> If you are working on small applications with a minimal number of
> databases on the DB server then you may see some performance improvement
> (but tbh not as much as you used to – as the servers have changed)
> Unfortunately I don’t in both my main and secondary roles, and I know many
> others who come across these limitations as well.
>
> I’m not saying don’t use persistent or cached connections – but leaving it
> to some hidden layers is not necessarily a good thing to do – it can have
> unforeseen side effects {and Apache::DBI & PHP pconnect have both shown
> these up}
>
> If you are working with e.g. with MySQL the overhead of the (socket)
> connection is very small, but having more connections open to cope with
> persistent connections {memory wise} often needs specifying a much large
> database server – or not being able to do all the nice tricks to in memory
> indexes and queries [to increase query performance]. Being able to chose
> which connections you keep open and which you open/close on a per request
> basis gives you the benefits of caching without the risks involved [other
> than the “lock table” issue].
>
>
>
>
>
> *From:* Mithun Bhattacharya <mi...@gmail.com>
> *Sent:* 09 February 2021 18:34
> *To:* mod_perl list <mo...@perl.apache.org>
> *Subject:* Re: Moving ExecCGI to mod_perl - performance and custom
> 'modules' [EXT]
>
>
>
> Connection caching does work for most use cases - we have to accept James
> works in scenarios most developers can't fathom :)
>
>
>
> If you are just firing off simple SQL's without any triggers or named
> temporary tables involved you should be good. The only times we recall
> tripping on cached connection is when two different code snippets tried to
> create the same temporary table. Another time the code was expecting the
> disconnect to complete the connection cleanup.
>
>
>
> On Tue, Feb 9, 2021 at 11:47 AM Vincent Veyron <vv...@wanadoo.fr>
> wrote:
>
> On Sun, 7 Feb 2021 20:21:34 +0000
> James Smith <js...@sanger.ac.uk> wrote:
>
> Hi James,
>
> > DBI sharing doesn't really gain you much - and can actually lead you
> into a whole world of pain. It isn't actually worth turning it on at all.
> >
>
> Never had a problem with it myself in years of using it, but I wrap my
> queries in an eval { } and check $@, so that the scripts are not left
> hanging; also I have a postgresql db ;-).
>
> I ran some tests with ab, I do see an improvement in response speed :
>
> my $dbh = DBI->connect()
> Concurrency Level: 5
> Time taken for tests: 22.198 seconds
> Complete requests: 1000
> Failed requests: 0
> Total transferred: 8435000 bytes
> HTML transferred: 8176000 bytes
> Requests per second: 45.05 [#/sec] (mean)
> Time per request: 110.990 [ms] (mean)
> Time per request: 22.198 [ms] (mean, across all concurrent requests)
> Transfer rate: 371.08 [Kbytes/sec] received
>
> my $dbh = DBI->connect_cached()
> Concurrency Level: 5
> Time taken for tests: 15.133 seconds
> Complete requests: 1000
> Failed requests: 0
> Total transferred: 8435000 bytes
> HTML transferred: 8176000 bytes
> Requests per second: 66.08 [#/sec] (mean)
> Time per request: 75.664 [ms] (mean)
> Time per request: 15.133 [ms] (mean, across all concurrent requests)
> Transfer rate: 544.33 [Kbytes/sec] received
>
>
> --
>
> Bien à vous, Vincent Veyron
>
> https://compta.libremen.com [compta.libremen.com]
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__compta.libremen.com&d=DwMFaQ&c=D7ByGjS34AllFgecYw0iC6Zq7qlm8uclZFI0SqQnqBo&r=oH2yp0ge1ecj4oDX0XM7vQ&m=CnIW-j3Bw_IfohZCciiwtkoqvr6nV2hHrNYMPpEOe8E&s=uf6Qi4tnTPryVuPvOKwfZQcFOksecWyn-LYPDVj44lY&e=>
> Logiciel libre de comptabilité générale en partie double
>
>
> -- The Wellcome Sanger Institute is operated by Genome Research Limited, a
> charity registered in England with number 1021457 and a company registered
> in England with number 2742969, whose registered office is 215 Euston Road,
> London, NW1 2BE.
>
RE: Moving ExecCGI to mod_perl - performance and custom 'modules'
[EXT]
Posted by James Smith <js...@sanger.ac.uk>.
Mithun,
I’m not sure on what scale you work – but these are from experience in sites with small to medium load – and we rarely see an appreciable gain in using cached or pooled connections, just the occasional heartache they cause.
If you are working on small applications with a minimal number of databases on the DB server then you may see some performance improvement (but tbh not as much as you used to – as the servers have changed) Unfortunately I don’t in both my main and secondary roles, and I know many others who come across these limitations as well.
I’m not saying don’t use persistent or cached connections – but leaving it to some hidden layers is not necessarily a good thing to do – it can have unforeseen side effects {and Apache::DBI & PHP pconnect have both shown these up}
If you are working with e.g. with MySQL the overhead of the (socket) connection is very small, but having more connections open to cope with persistent connections {memory wise} often needs specifying a much large database server – or not being able to do all the nice tricks to in memory indexes and queries [to increase query performance]. Being able to chose which connections you keep open and which you open/close on a per request basis gives you the benefits of caching without the risks involved [other than the “lock table” issue].
From: Mithun Bhattacharya <mi...@gmail.com>
Sent: 09 February 2021 18:34
To: mod_perl list <mo...@perl.apache.org>
Subject: Re: Moving ExecCGI to mod_perl - performance and custom 'modules' [EXT]
Connection caching does work for most use cases - we have to accept James works in scenarios most developers can't fathom :)
If you are just firing off simple SQL's without any triggers or named temporary tables involved you should be good. The only times we recall tripping on cached connection is when two different code snippets tried to create the same temporary table. Another time the code was expecting the disconnect to complete the connection cleanup.
On Tue, Feb 9, 2021 at 11:47 AM Vincent Veyron <vv...@wanadoo.fr>> wrote:
On Sun, 7 Feb 2021 20:21:34 +0000
James Smith <js...@sanger.ac.uk>> wrote:
Hi James,
> DBI sharing doesn't really gain you much - and can actually lead you into a whole world of pain. It isn't actually worth turning it on at all.
>
Never had a problem with it myself in years of using it, but I wrap my queries in an eval { } and check $@, so that the scripts are not left hanging; also I have a postgresql db ;-).
I ran some tests with ab, I do see an improvement in response speed :
my $dbh = DBI->connect()
Concurrency Level: 5
Time taken for tests: 22.198 seconds
Complete requests: 1000
Failed requests: 0
Total transferred: 8435000 bytes
HTML transferred: 8176000 bytes
Requests per second: 45.05 [#/sec] (mean)
Time per request: 110.990 [ms] (mean)
Time per request: 22.198 [ms] (mean, across all concurrent requests)
Transfer rate: 371.08 [Kbytes/sec] received
my $dbh = DBI->connect_cached()
Concurrency Level: 5
Time taken for tests: 15.133 seconds
Complete requests: 1000
Failed requests: 0
Total transferred: 8435000 bytes
HTML transferred: 8176000 bytes
Requests per second: 66.08 [#/sec] (mean)
Time per request: 75.664 [ms] (mean)
Time per request: 15.133 [ms] (mean, across all concurrent requests)
Transfer rate: 544.33 [Kbytes/sec] received
--
Bien à vous, Vincent Veyron
https://compta.libremen.com [compta.libremen.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__compta.libremen.com&d=DwMFaQ&c=D7ByGjS34AllFgecYw0iC6Zq7qlm8uclZFI0SqQnqBo&r=oH2yp0ge1ecj4oDX0XM7vQ&m=CnIW-j3Bw_IfohZCciiwtkoqvr6nV2hHrNYMPpEOe8E&s=uf6Qi4tnTPryVuPvOKwfZQcFOksecWyn-LYPDVj44lY&e=>
Logiciel libre de comptabilité générale en partie double
--
The Wellcome Sanger Institute is operated by Genome Research
Limited, a charity registered in England with number 1021457 and a
company registered in England with number 2742969, whose registered
office is 215 Euston Road, London, NW1 2BE.
Re: Moving ExecCGI to mod_perl - performance and custom 'modules' [EXT]
Posted by Mithun Bhattacharya <mi...@gmail.com>.
Connection caching does work for most use cases - we have to accept James
works in scenarios most developers can't fathom :)
If you are just firing off simple SQL's without any triggers or named
temporary tables involved you should be good. The only times we recall
tripping on cached connection is when two different code snippets tried to
create the same temporary table. Another time the code was expecting the
disconnect to complete the connection cleanup.
On Tue, Feb 9, 2021 at 11:47 AM Vincent Veyron <vv...@wanadoo.fr> wrote:
> On Sun, 7 Feb 2021 20:21:34 +0000
> James Smith <js...@sanger.ac.uk> wrote:
>
> Hi James,
>
> > DBI sharing doesn't really gain you much - and can actually lead you
> into a whole world of pain. It isn't actually worth turning it on at all.
> >
>
> Never had a problem with it myself in years of using it, but I wrap my
> queries in an eval { } and check $@, so that the scripts are not left
> hanging; also I have a postgresql db ;-).
>
> I ran some tests with ab, I do see an improvement in response speed :
>
> my $dbh = DBI->connect()
> Concurrency Level: 5
> Time taken for tests: 22.198 seconds
> Complete requests: 1000
> Failed requests: 0
> Total transferred: 8435000 bytes
> HTML transferred: 8176000 bytes
> Requests per second: 45.05 [#/sec] (mean)
> Time per request: 110.990 [ms] (mean)
> Time per request: 22.198 [ms] (mean, across all concurrent requests)
> Transfer rate: 371.08 [Kbytes/sec] received
>
> my $dbh = DBI->connect_cached()
> Concurrency Level: 5
> Time taken for tests: 15.133 seconds
> Complete requests: 1000
> Failed requests: 0
> Total transferred: 8435000 bytes
> HTML transferred: 8176000 bytes
> Requests per second: 66.08 [#/sec] (mean)
> Time per request: 75.664 [ms] (mean)
> Time per request: 15.133 [ms] (mean, across all concurrent requests)
> Transfer rate: 544.33 [Kbytes/sec] received
>
>
> --
>
> Bien à vous, Vincent Veyron
>
> https://compta.libremen.com
> Logiciel libre de comptabilité générale en partie double
>
>
>
>
Re: Moving ExecCGI to mod_perl - performance and custom 'modules'
[EXT]
Posted by Vincent Veyron <vv...@wanadoo.fr>.
On Sun, 7 Feb 2021 20:21:34 +0000
James Smith <js...@sanger.ac.uk> wrote:
Hi James,
> DBI sharing doesn't really gain you much - and can actually lead you into a whole world of pain. It isn't actually worth turning it on at all.
>
Never had a problem with it myself in years of using it, but I wrap my queries in an eval { } and check $@, so that the scripts are not left hanging; also I have a postgresql db ;-).
I ran some tests with ab, I do see an improvement in response speed :
my $dbh = DBI->connect()
Concurrency Level: 5
Time taken for tests: 22.198 seconds
Complete requests: 1000
Failed requests: 0
Total transferred: 8435000 bytes
HTML transferred: 8176000 bytes
Requests per second: 45.05 [#/sec] (mean)
Time per request: 110.990 [ms] (mean)
Time per request: 22.198 [ms] (mean, across all concurrent requests)
Transfer rate: 371.08 [Kbytes/sec] received
my $dbh = DBI->connect_cached()
Concurrency Level: 5
Time taken for tests: 15.133 seconds
Complete requests: 1000
Failed requests: 0
Total transferred: 8435000 bytes
HTML transferred: 8176000 bytes
Requests per second: 66.08 [#/sec] (mean)
Time per request: 75.664 [ms] (mean)
Time per request: 15.133 [ms] (mean, across all concurrent requests)
Transfer rate: 544.33 [Kbytes/sec] received
--
Bien à vous, Vincent Veyron
https://compta.libremen.com
Logiciel libre de comptabilité générale en partie double
Re: Moving ExecCGI to mod_perl - performance and custom 'modules' [EXT]
Posted by John Dunlap <Jo...@lariat.co>.
We're in a similar situation with 20-40 databases per server. We use
PGBouncer for connection pooling.
On Sun, Feb 7, 2021 at 2:23 PM James Smith <js...@sanger.ac.uk> wrote:
> DBI sharing doesn't really gain you much - and can actually lead you into
> a whole world of pain. It isn't actually worth turning it on at all.
>
> We use dedicated DB caching in the cases where we benefit from it as and
> when you need it (low level caching database)...
>
> Although milage may vary - our problem was DB servers with 30 or 40
> databases on them being connected from a number of approximately 50-100
> child apaches, meant we ended up blowing up the connections to the database
> server really quickly...
>
>
> -----Original Message-----
> From: Vincent Veyron <vv...@wanadoo.fr>
> Sent: 07 February 2021 19:06
> To: Steven Haigh <ne...@crc.id.au>
> Cc: James Smith <js...@sanger.ac.uk>; modperl@perl.apache.org
> Subject: Re: Moving ExecCGI to mod_perl - performance and custom 'modules'
> [EXT]
>
> On Sun, 07 Feb 2021 23:58:17 +1100
> Steven Haigh <ne...@crc.id.au> wrote:
> >
> > I haven't gotten into the preload or DBI sharing yet - as that'll end
> > up needing a bit of a rewrite of code to take advantage of. I'd be
> > open to suggestions here from those who have done it in the past to
> > save me going down some dead ends :D
>
> I use mod_perl handlers, so not sure how it mixes with PerlRegistry, but
> you probably want to have a look at connect_cached
>
>
> --
>
> Bien à vous, Vincent Veyron
>
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__compta.libremen.com&d=DwIFAw&c=D7ByGjS34AllFgecYw0iC6Zq7qlm8uclZFI0SqQnqBo&r=oH2yp0ge1ecj4oDX0XM7vQ&m=C0OcuGbNbfxaSa8ASgV3uFXzejn7MpjIUH1aP1RbiyU&s=GPr8VuKQ3rZCzCPwggyAHdCOojK6ZThmShKk0Jb3maI&e=
> Logiciel libre de comptabilité générale en partie double
>
>
>
> --
> The Wellcome Sanger Institute is operated by Genome Research
> Limited, a charity registered in England with number 1021457 and a
> company registered in England with number 2742969, whose registered
> office is 215 Euston Road, London, NW1 2BE.
>
--
John Dunlap
*CTO | Lariat *
*Direct:*
*john@lariat.co <jo...@lariat.co>*
*Customer Service:*
877.268.6667
support@lariat.co
RE: Moving ExecCGI to mod_perl - performance and custom 'modules'
[EXT]
Posted by James Smith <js...@sanger.ac.uk>.
No it was one of our DBAs who told us to take if off…! It causes them all sorts of problems – the main one being it keeps connections open, which is the best way to completely foobar the database servers! We make them happy by turning it off. We’ve even had Oracle developers (sorry not people developing SQL in oracle but people developing Oracle) scratching their heads over things like this and not being able to come up with a solution…..
We’ve discovered lots of interesting side effects with connection pooling when using over a secure network – e.g. the Oracle client doesn’t like running through a firewall – as it can’t cope when the firewall drops the connection – both sides of the system the “pool” thinks the connection is open, the database thinks the connection is open, and the client just hangs….. We have seen similar things with other applications which use connection pooling and long duration database handles. We get round it with permanent MySQL connections by closing/re-opening them after 5 minutes of inactivity – hence the need to develop our own cache/pool….
From: Mithun Bhattacharya <mi...@gmail.com>
Sent: 07 February 2021 20:36
To: James Smith <js...@sanger.ac.uk>
Cc: Vincent Veyron <vv...@wanadoo.fr>; Steven Haigh <ne...@crc.id.au>; modperl@perl.apache.org
Subject: Re: Moving ExecCGI to mod_perl - performance and custom 'modules' [EXT]
DBI sharing has it's own issues but in most use cases it does a pretty good job and keeps the DBA's happy - that is very important ;)
On Sun, Feb 7, 2021 at 2:23 PM James Smith <js...@sanger.ac.uk>> wrote:
DBI sharing doesn't really gain you much - and can actually lead you into a whole world of pain. It isn't actually worth turning it on at all.
We use dedicated DB caching in the cases where we benefit from it as and when you need it (low level caching database)...
Although milage may vary - our problem was DB servers with 30 or 40 databases on them being connected from a number of approximately 50-100 child apaches, meant we ended up blowing up the connections to the database server really quickly...
-----Original Message-----
From: Vincent Veyron <vv...@wanadoo.fr>>
Sent: 07 February 2021 19:06
To: Steven Haigh <ne...@crc.id.au>>
Cc: James Smith <js...@sanger.ac.uk>>; modperl@perl.apache.org<ma...@perl.apache.org>
Subject: Re: Moving ExecCGI to mod_perl - performance and custom 'modules' [EXT]
On Sun, 07 Feb 2021 23:58:17 +1100
Steven Haigh <ne...@crc.id.au>> wrote:
>
> I haven't gotten into the preload or DBI sharing yet - as that'll end
> up needing a bit of a rewrite of code to take advantage of. I'd be
> open to suggestions here from those who have done it in the past to
> save me going down some dead ends :D
I use mod_perl handlers, so not sure how it mixes with PerlRegistry, but you probably want to have a look at connect_cached
--
Bien à vous, Vincent Veyron
https://urldefense.proofpoint.com/v2/url?u=https-3A__compta.libremen.com&d=DwIFAw&c=D7ByGjS34AllFgecYw0iC6Zq7qlm8uclZFI0SqQnqBo&r=oH2yp0ge1ecj4oDX0XM7vQ&m=C0OcuGbNbfxaSa8ASgV3uFXzejn7MpjIUH1aP1RbiyU&s=GPr8VuKQ3rZCzCPwggyAHdCOojK6ZThmShKk0Jb3maI&e=
Logiciel libre de comptabilité générale en partie double
--
The Wellcome Sanger Institute is operated by Genome Research
Limited, a charity registered in England with number 1021457 and a
company registered in England with number 2742969, whose registered
office is 215 Euston Road, London, NW1 2BE.
--
The Wellcome Sanger Institute is operated by Genome Research
Limited, a charity registered in England with number 1021457 and a
company registered in England with number 2742969, whose registered
office is 215 Euston Road, London, NW1 2BE.
Re: Moving ExecCGI to mod_perl - performance and custom 'modules' [EXT]
Posted by Mithun Bhattacharya <mi...@gmail.com>.
DBI sharing has it's own issues but in most use cases it does a pretty good
job and keeps the DBA's happy - that is very important ;)
On Sun, Feb 7, 2021 at 2:23 PM James Smith <js...@sanger.ac.uk> wrote:
> DBI sharing doesn't really gain you much - and can actually lead you into
> a whole world of pain. It isn't actually worth turning it on at all.
>
> We use dedicated DB caching in the cases where we benefit from it as and
> when you need it (low level caching database)...
>
> Although milage may vary - our problem was DB servers with 30 or 40
> databases on them being connected from a number of approximately 50-100
> child apaches, meant we ended up blowing up the connections to the database
> server really quickly...
>
>
> -----Original Message-----
> From: Vincent Veyron <vv...@wanadoo.fr>
> Sent: 07 February 2021 19:06
> To: Steven Haigh <ne...@crc.id.au>
> Cc: James Smith <js...@sanger.ac.uk>; modperl@perl.apache.org
> Subject: Re: Moving ExecCGI to mod_perl - performance and custom 'modules'
> [EXT]
>
> On Sun, 07 Feb 2021 23:58:17 +1100
> Steven Haigh <ne...@crc.id.au> wrote:
> >
> > I haven't gotten into the preload or DBI sharing yet - as that'll end
> > up needing a bit of a rewrite of code to take advantage of. I'd be
> > open to suggestions here from those who have done it in the past to
> > save me going down some dead ends :D
>
> I use mod_perl handlers, so not sure how it mixes with PerlRegistry, but
> you probably want to have a look at connect_cached
>
>
> --
>
> Bien à vous, Vincent Veyron
>
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__compta.libremen.com&d=DwIFAw&c=D7ByGjS34AllFgecYw0iC6Zq7qlm8uclZFI0SqQnqBo&r=oH2yp0ge1ecj4oDX0XM7vQ&m=C0OcuGbNbfxaSa8ASgV3uFXzejn7MpjIUH1aP1RbiyU&s=GPr8VuKQ3rZCzCPwggyAHdCOojK6ZThmShKk0Jb3maI&e=
> Logiciel libre de comptabilité générale en partie double
>
>
>
> --
> The Wellcome Sanger Institute is operated by Genome Research
> Limited, a charity registered in England with number 1021457 and a
> company registered in England with number 2742969, whose registered
> office is 215 Euston Road, London, NW1 2BE.
>
RE: Moving ExecCGI to mod_perl - performance and custom 'modules'
[EXT]
Posted by James Smith <js...@sanger.ac.uk>.
I meant between requests in the same thread – it uses persistent connections which are bad in a number of ways {e.g. fun with locking if you use it and your script dies halfway through, keeps too many connections open and can block the database, has issues with secure set ups {firewall between web and servers for instance}
From: Wesley Peng <we...@pengfamily.de>
Sent: 08 February 2021 00:29
To: modperl@perl.apache.org
Subject: Re: Moving ExecCGI to mod_perl - performance and custom 'modules' [EXT]
what's DBI sharing? do you mean Apache::DBI?
Does perl has Java similar DB connection pool?
Thanks.
On Mon, Feb 8, 2021, at 4:21 AM, James Smith wrote:
DBI sharing doesn't really gain you much - and can actually lead you into a whole world of pain. It isn't actually worth turning it on at all.
We use dedicated DB caching in the cases where we benefit from it as and when you need it (low level caching database)...
Although milage may vary - our problem was DB servers with 30 or 40 databases on them being connected from a number of approximately 50-100 child apaches, meant we ended up blowing up the connections to the database server really quickly...
-----Original Message-----
From: Vincent Veyron <vv...@wanadoo.fr>>
Sent: 07 February 2021 19:06
To: Steven Haigh <ne...@crc.id.au>>
Cc: James Smith <js...@sanger.ac.uk>>; modperl@perl.apache.org<ma...@perl.apache.org>
Subject: Re: Moving ExecCGI to mod_perl - performance and custom 'modules' [EXT]
On Sun, 07 Feb 2021 23:58:17 +1100
Steven Haigh <ne...@crc.id.au>> wrote:
>
> I haven't gotten into the preload or DBI sharing yet - as that'll end
> up needing a bit of a rewrite of code to take advantage of. I'd be
> open to suggestions here from those who have done it in the past to
> save me going down some dead ends :D
I use mod_perl handlers, so not sure how it mixes with PerlRegistry, but you probably want to have a look at connect_cached
--
Bien à vous, Vincent Veyron
https://urldefense.proofpoint.com/v2/url?u=https-3A__compta.libremen.com&d=DwIFAw&c=D7ByGjS34AllFgecYw0iC6Zq7qlm8uclZFI0SqQnqBo&r=oH2yp0ge1ecj4oDX0XM7vQ&m=C0OcuGbNbfxaSa8ASgV3uFXzejn7MpjIUH1aP1RbiyU&s=GPr8VuKQ3rZCzCPwggyAHdCOojK6ZThmShKk0Jb3maI&e=
Logiciel libre de comptabilité générale en partie double
--
The Wellcome Sanger Institute is operated by Genome Research
Limited, a charity registered in England with number 1021457 and a
company registered in England with number 2742969, whose registered
office is 215 Euston Road, London, NW1 2BE.
--
The Wellcome Sanger Institute is operated by Genome Research
Limited, a charity registered in England with number 1021457 and a
company registered in England with number 2742969, whose registered
office is 215 Euston Road, London, NW1 2BE.
Re: Moving ExecCGI to mod_perl - performance and custom 'modules' [EXT]
Posted by Wesley Peng <we...@pengfamily.de>.
what's DBI sharing? do you mean Apache::DBI?
Does perl has Java similar DB connection pool?
Thanks.
On Mon, Feb 8, 2021, at 4:21 AM, James Smith wrote:
> DBI sharing doesn't really gain you much - and can actually lead you into a whole world of pain. It isn't actually worth turning it on at all.
>
> We use dedicated DB caching in the cases where we benefit from it as and when you need it (low level caching database)...
>
> Although milage may vary - our problem was DB servers with 30 or 40 databases on them being connected from a number of approximately 50-100 child apaches, meant we ended up blowing up the connections to the database server really quickly...
>
>
> -----Original Message-----
> From: Vincent Veyron <vv...@wanadoo.fr>
> Sent: 07 February 2021 19:06
> To: Steven Haigh <ne...@crc.id.au>
> Cc: James Smith <js...@sanger.ac.uk>; modperl@perl.apache.org
> Subject: Re: Moving ExecCGI to mod_perl - performance and custom 'modules' [EXT]
>
> On Sun, 07 Feb 2021 23:58:17 +1100
> Steven Haigh <ne...@crc.id.au> wrote:
> >
> > I haven't gotten into the preload or DBI sharing yet - as that'll end
> > up needing a bit of a rewrite of code to take advantage of. I'd be
> > open to suggestions here from those who have done it in the past to
> > save me going down some dead ends :D
>
> I use mod_perl handlers, so not sure how it mixes with PerlRegistry, but you probably want to have a look at connect_cached
>
>
> --
>
> Bien à vous, Vincent Veyron
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__compta.libremen.com&d=DwIFAw&c=D7ByGjS34AllFgecYw0iC6Zq7qlm8uclZFI0SqQnqBo&r=oH2yp0ge1ecj4oDX0XM7vQ&m=C0OcuGbNbfxaSa8ASgV3uFXzejn7MpjIUH1aP1RbiyU&s=GPr8VuKQ3rZCzCPwggyAHdCOojK6ZThmShKk0Jb3maI&e=
> Logiciel libre de comptabilité générale en partie double
>
>
>
> --
> The Wellcome Sanger Institute is operated by Genome Research
> Limited, a charity registered in England with number 1021457 and a
> company registered in England with number 2742969, whose registered
> office is 215 Euston Road, London, NW1 2BE.
>
RE: Moving ExecCGI to mod_perl - performance and custom 'modules'
[EXT]
Posted by James Smith <js...@sanger.ac.uk>.
DBI sharing doesn't really gain you much - and can actually lead you into a whole world of pain. It isn't actually worth turning it on at all.
We use dedicated DB caching in the cases where we benefit from it as and when you need it (low level caching database)...
Although milage may vary - our problem was DB servers with 30 or 40 databases on them being connected from a number of approximately 50-100 child apaches, meant we ended up blowing up the connections to the database server really quickly...
-----Original Message-----
From: Vincent Veyron <vv...@wanadoo.fr>
Sent: 07 February 2021 19:06
To: Steven Haigh <ne...@crc.id.au>
Cc: James Smith <js...@sanger.ac.uk>; modperl@perl.apache.org
Subject: Re: Moving ExecCGI to mod_perl - performance and custom 'modules' [EXT]
On Sun, 07 Feb 2021 23:58:17 +1100
Steven Haigh <ne...@crc.id.au> wrote:
>
> I haven't gotten into the preload or DBI sharing yet - as that'll end
> up needing a bit of a rewrite of code to take advantage of. I'd be
> open to suggestions here from those who have done it in the past to
> save me going down some dead ends :D
I use mod_perl handlers, so not sure how it mixes with PerlRegistry, but you probably want to have a look at connect_cached
--
Bien à vous, Vincent Veyron
https://urldefense.proofpoint.com/v2/url?u=https-3A__compta.libremen.com&d=DwIFAw&c=D7ByGjS34AllFgecYw0iC6Zq7qlm8uclZFI0SqQnqBo&r=oH2yp0ge1ecj4oDX0XM7vQ&m=C0OcuGbNbfxaSa8ASgV3uFXzejn7MpjIUH1aP1RbiyU&s=GPr8VuKQ3rZCzCPwggyAHdCOojK6ZThmShKk0Jb3maI&e=
Logiciel libre de comptabilité générale en partie double
--
The Wellcome Sanger Institute is operated by Genome Research
Limited, a charity registered in England with number 1021457 and a
company registered in England with number 2742969, whose registered
office is 215 Euston Road, London, NW1 2BE.