>The problem here is I believe we are using a different definition of
>quality. For me, something is "good" as long as it does what I want it to
>do.
Ok, I understand what your arguments boils down to now (but my definition
is actually exactly the same as yours ;). Let me refine my self:
I d
27289C630288B34E@mail1">news:27E647E5629ED211BF78009027289C630288B34E@mail1...
>
> >-Original Message-
> >From: Plutarck [mailto:[EMAIL PROTECTED]]
> >Sent: Monday, April 16, 2001 8:53 AM
> >To: [EMAIL PROTECTED]
> >Subject: Re: Re[2]: [PHP-WIN] My
>-Original Message-
>From: Plutarck [mailto:[EMAIL PROTECTED]]
>Sent: Monday, April 16, 2001 8:53 AM
>To: [EMAIL PROTECTED]
>Subject: Re: Re[2]: [PHP-WIN] MySql pconnect
>
>
>As expressed in the article, the question is what the database
>was designed to
>-Original Message-
>From: Joe Brown [mailto:[EMAIL PROTECTED]]
>Sent: Sunday, April 15, 2001 8:53 PM
>But my point is that the communication overhead is still gained by process
>based systems. True they don't have the same pooling ability, as does a
>threaded process management. Over
As expressed in the article, the question is what the database was designed
to actually "do".
MySQL creates quick connections, responds to SELECT statements as fast as
anything can, has a small footprint, and does not require any special fees
to use it. And yes, it's open source. For the vast maj
i'm going to specify at apache now :)
Sunday, April 15, 2001, 8:52:59 PM, you wrote:
> But my point is that the communication overhead is still gained by process
> based systems. True they don't have the same pooling ability, as does a
> threaded process management. Overhead saved using pconnec
But my point is that the communication overhead is still gained by process
based systems. True they don't have the same pooling ability, as does a
threaded process management. Overhead saved using pconnect is that which is
being debated here.
On a side note The OCI8 module in it's latest r
Sunday, April 15, 2001, 6:45:14 PM, you wrote:
> Your comment reguarding threaded sapi's although accurate, leaves
> out
> process based systems. They also benefit from pconnects, because
> the PHP
> process lives on past the life of a single web page.
such things can't be shared amongst process
>-Original Message-
>From: Plutarck []
>http://www.webtechniques.com/archives/2001/01/jagielski/
>
>Skip down to where it mentions databases...very enlightening.
Yeah... MySQL is even a worse RDBM's than I thought since before.
No stored procedure, no transactions, no jezus!!!
--
http://www.webtechniques.com/archives/2001/01/jagielski/
Skip down to where it mentions databases...very enlightening.
I think I may just consider slipping a "p" into my db_connect() function :)
--
Plutarck
Should be working on something...
...but forgot what it was.
"Daniel Beulshausen" <[E
Sunday, April 15, 2001, 3:38:48 PM, you wrote:
> When you call pconnect when a persistant connection is already available, it
> is approximately the same speed as when you call connect for the second time
> in a script. It still is a delay. It's not "instant", because PHP has to
> check and see if
Hm...ok, let's see here. Persistant connection vs. non.
Pros and cons...*ponder*
I haven't heard a whole lot about the debate, but here is what I'm thinking.
When you call pconnect when a persistant connection is already available, it
is approximately the same speed as when you call connect for
I agree with James on this one - surely it makes sense if php is running as
a server module and can keep hold of connections to utilise the performance
advantage of pconnect.
I'd be interested to know if there are any disadvantages to this, I may need
to change some code :)
Cheers
--
Phil Drisco
>
> For connect vs. pconnect, the instances where you should use pconnect are
> really rare.
>
> When in doubt, use connect. If you know of a specifically good
> reason to use
> it, then feel free.
>
> But I personally have never had a situation where pconnect worked better
> than connect.
pco
For connect vs. pconnect, the instances where you should use pconnect are
really rare.
When in doubt, use connect. If you know of a specifically good reason to use
it, then feel free.
But I personally have never had a situation where pconnect worked better
than connect.
And as for extended serv
Hi
Can anyone tell me if it is better to use pconnect or connect for mysql, when I run
my site eventually on a linux server, with apache, php4?
And does anyone know anything about extended server status in MySql? Things run
alot better with this off when developing on win98.
Thanks
Xon
16 matches
Mail list logo
