Nothing wrong with MySQL. My comment was not specific to any particular
database. It was just a general comment that any database-backed web site
will have the database as the bottleneck and any little optimizations you
try to do at the scripting level is not going to matter much in the
grander scheme of things. You need to concentrate on making an efficient
schema and making sure you eliminate table-scans, etc.
-Rasmus
On Fri, 13 Jul 2001, Yves Gauvreau wrote:
> Is that to say that mySQL is not a good choice in this situation?
>
> If you would be so kind. Why would mySQL be the bottleneck and why PHP
> would not?
>
> Regards.
>
> Yves
>
>
> Rasmus Lerdorf wrote:
>
> > Should be fine. Chances are your bottleneck will be your database, not
> > PHP.
> >
> > -Rasmus
> >
> > On Fri, 13 Jul 2001, Yves Gauvreau wrote:
> >
> >
> >>Hi,
> >>
> >>The question is this: Say I have a large main script that handles most
> >>of the request if not all, I wonder what are the effect of this approach
> >>on performance in a situation where we have a fair number of concurrent
> >>users?
> >>
> >>Situation:
> >>
> >>Server:
> >>P4 1300, Linux (RH 7.1), Apache, MOD_PHP, mySQL.
> >>
> >>Thanks
> >>
> >>Yves Gauvreau
> >>
> >>
> >>
> >>
> >
>
>
>
>
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
