php3-list | 200003
Date: 03/30/00
- Next message: Jeroen Keppens: "Re: [PHP3] Search"
- Previous message: Manuel Lemos: "Re: [PHP3] Getting values of dynamically constructed form variable names"
- In reply to: Samantha Savvakis: "[PHP3] Scalability"
- Next in thread: Kristian Köhntopp: "Re: [PHP3] Scalability"
- Reply: Kristian Köhntopp: "Re: [PHP3] Scalability"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hello Samantha,
On 30-Mar-00 00:21:27, you wrote:
>Hi,
>I'm in a debate with a friend of mine who claims this following statement:
>"I looked into all the tech, and forget hype for a sec and look at just the
>technical details. PHP is good, but it doesn't scale up to major sites in
>order or 500,000 users or so".
500,000 users? What's that 500,000 simultaneous users? I don't know a
site in the world that handles that much simultaneous users? Maybe 500,000
users/page views/hits a day, no problem.
>Now, what I'd like to know is, how scalable is a site based on PHP and where
>does this guy get off saying such things? He seems to think that JSP kicks
>butt and PHP doesn't stand a chance against it. So, I need a good comeback
>about PHP because I think it's great!
The solution is not in the language but in the way you serve your pages.
If the content doesn't change much, it is worthy of being cached even if
they has to be regenerated online regularly.
Before even thinking of serving the page contents you should ask if your
server is serving static content efficiently and if you really need to
serve that much decoration like floods of graphics.
>From the server standpoint, using less images is more important than using
smaller images. Each image in the page makes the browser open a connection
in a page. It's a common mistake to stuff single pages with tens of
different images.
A single access to pages like that make the server fork tens of processes
to serve the images and that happens. Many simultaneous to a page like
that may overload your server in no time, regardless if the page is static
or dynamically generated by PHP, JSP, whatever...
Among many other server tuning options, you may want to consider the static
content caching options that exist like using mod_mmap_magic with Apache.
Other than that you may want to use PHP 4 instead of PHP 3 for such heavy
load sites. The unoptimized version of PHP 4 is already much faster than
PHP 3. If your pages have some processing that is not so light, the Zend
Optimizer extension may make a difference. In the future there will be a
also a cache extension that caches compiled scripts in memory and that also
will make a difference.
Even if PHP needs these add-ons, I'm sure it will beat JSP because AFAIK
JSP needs relies a lot on IPC between the Web server and JVM and PHP may be
built in to the Web server.
Regards,
Manuel Lemos
Web Programming Components using PHP Classes.
Look at: email protected>?subject=Re:%20[PHP3]%20Scalability&replyto=2652.124T2521T2405502mlemos <email protected>">mlemos <email protected>">http://phpclasses.UpperDesign.com/?user=mlemos <email protected>
-- E-mail: mlemos <email protected> URL: http://www.mlemos.e-na.net/ PGP key: http://www.mlemos.e-na.net/ManuelLemos.pgp ---- PHP 3 Mailing List <http://www.php.net/> To unsubscribe, send an empty message to php3-unsubscribe <email protected> To subscribe to the digest, e-mail: php3-digest-subscribe <email protected> To search the mailing list archive, go to: http://www.php.net/mailsearch.php3 To contact the list administrators, e-mail: php-list-admin <email protected>
- Next message: Jeroen Keppens: "Re: [PHP3] Search"
- Previous message: Manuel Lemos: "Re: [PHP3] Getting values of dynamically constructed form variable names"
- In reply to: Samantha Savvakis: "[PHP3] Scalability"
- Next in thread: Kristian Köhntopp: "Re: [PHP3] Scalability"
- Reply: Kristian Köhntopp: "Re: [PHP3] Scalability"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

