Any large sites running on PHP4?

... or when NOT tu use PHP

[le_gber]

Just series of questions that srpung to my mind this late evening.

What is the maximum size for a dynamic site written in PHP/MySQL before it starts putting too much strain on the server?

I plan on building a site with a db having 10-20 tables with the two main ones having 10,000 entries max. Would they support a 15/20K requests per day or should I think about using another language? If so which one: ASP.Net, Perl, JSP, Coldfusion?

If I know in advance some of the queries that will be run, could I pre-run them and store them 'somewhere' to make them easier/quicker for the server to deliver?

Is PHP5 better for large scale apps - I was thinking of using PHP4?

Do you know of any large ecommerce website running on PHP?

Cheers

[jatar_k]

message 69 and 75 have some good lonks in this thread
[webmasterworld.com...]

from priidik
[public.yahoo.com...]

from amznVibe
[talks.php.net...]
[public.yahoo.com...]
[public.yahoo.com...]

[le_gber]

Hi jatar_k

thanks for the links.

---

On a 'different subject' I wondered what were the best practice of (PHP) code writing? Using stored procedures, caching (the other thread talk about caching), using includes for 'reusable' code?

What techniques do advanced PHP developers use to make the code leaner / faster and overall better?

How do you test your applications load on the server and how do you optimise the code to lower this load?

Cheers

[coopster]

Stored procedures are database processes, not PHP nor other development languages. This is probably the most effective place to make your site leaner and faster -- in the database processing. Designing the database for the application and indexing files correctly are two primary areas to focus. If you choose not to keep the 'content' parts of your pages in database tables but in system files instead you simply include those pieces and PHP will handle this with extreme efficiency too.

Reuse code? Absolutely. I maintain functions, often in classes, that allow code reuse. Flexible and fast. Single point of maintenance, single point where I can monitor for issues/errors, ... lots of advantages to this practice.

I also believe one of the biggest balances in an optimal site is knowing and setting up the http server correctly. This is often overlooked and shouldn't be. PHP and Apache configured correctly for your site and it's applications is very important. So it's not always the code you want to focus on. If you aren't using certain extensions, don't enable them, don't load them. This goes for both PHP and Apache.