Re: Re: Comparing ADODB with PEAR DB, Metabase andNative MySQL
| From: | Stig S. Bakken | Date: | Sat, 17 Nov 2001 08:52:40 +0000 |
| Subject: | Re: Re: Comparing ADODB with PEAR DB, Metabase andNative MySQL | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-2946@lists.php.net to get a copy of this message | ||
Jean-Michel POURE wrote:
>
> At 16:32 07/11/01 +0100, you wrote:
> >I went through these results and I was surprised, how PEAR is slow. I
> >hope that when DB will be rewriten to C, it will be faster. Can somebody
> >tell me when this will be? Or are you waiting then PEAR::DB will be
> >stabilized? Or is somebody working on it?
>
> I see no need in rewriting PEAR to C, this would be foolish.
>
> Some people think they will get faster results when using the latest
> hardware (a Pentium 10) and/or the best API (ex: C or ADODB). In the real
> world, this will only bring you little optimization. I use ADODB with some
> applications, but it make only 1% of the total application speed.
>
> Optimization can only be achieved at application level, i.e.
> - in your database structure,
> - in the core PHP code of your application.
>
> Using MySQL, you will never ever achieve good results. Try PostgreSQL with
> embedded PL/pgSQL language and triggers, this will multiply the speed by
> 10, at least.
Well, not everyone is using SQL databases, for some people (including
me), CPU is the real bottleneck.
Rewriting the "PEAR" class to C would IMHO not be foolish: it would save
basically everyone using PEAR from parsing ~800 lines of code for each
request, and it would speed up error handling and every other basic pear
function. To me, that's a well-invested optimization (since everyone
benefits from it).
- Stig