Sorry for the delay.
The project I'm working on is private by nature in the sence that only
my clients will have access to the application. I don't expect to have
more then a few dozen but each of them may have up to say 50 users. Say
I have 50 clients each with 50 users. This means that I could have as
much as 2500 concurrent users with an extremely low probability I'll
admit to that. The same goes for only 1 users at a time but I think this
situation is much more likely then all users at the same time. I don't
know the exact distribution but I suspect it's somekind of gamma
distribution with the peak (or mode) in the relatively low numbers. Also
the approach I'm taking will favor working with a low number of records
at a time, of course this can go as high as 10000 records in some case
but here again the mode of the distribution should be in the low
numbers. Lastly I think that about 50% of the request to the web server
will require database access.
In summary, when I'll be in full production I'm positive that I'll have
some number of concurrent users, how many exactly I don't know but I
would estimate it to be somewhere in the relatively low number range
maybe 2-5 with peaks up to 20. I estimate that the server will be
working about 4 hours a day most of it in the day shift (6am ~ 6pm), the
rest of the time it will be waiting for request or at some internal stuff.
Regards.
Yves Gauvreau
Chris Lambert - Whitecrown Networks wrote:
> It all depends on your application, the use it receives, your server
> hardware (mainly RAM), and your MySQL/PHP configurations.
>
> For 90% of web applications, and 90% of the loads they receive, any
> confiuguration of MySQL would be fine. But describe your scenario and we
> should be able to let you know if all will be OK.
>
> /* Chris Lambert, CTO - [EMAIL PROTECTED]
> WhiteCrown Networks - More Than White Hats
> Web Application Security - www.whitecrown.net
> */
>
> ----- Original Message -----
> From: Yves Gauvreau <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>; Rasmus Lerdorf <[EMAIL PROTECTED]>
> Sent: Friday, July 13, 2001 5:48 PM
> Subject: Re: [PHP] Web application?
>
>
> | 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]
> |
> |
> |
>
>
--
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]
