problems due to large number of sql queries in a php page

Of course, if your site gets bigger, you will have problems putting everything on one page. That's logic, and you can't change it.

Different solutions:

• Pagination: you could create a pagination system (plenty of tutorials out there... http://net.tutsplus.com/tutorials/php/how-to-paginate-data-with-php/)
• If it's possible, divide your pages. Don't have all the comments on one and only one page. Try to have different pages, with different type of data, so it'll divide the load.

It's obvious that if your database gets too big, it'll be impossible to simply dump all the data on one page. Even the quickest browsers would crash.

One thing what you can do is Memcached. It will store in cache those results. So for the next visitor, who chick on the same page will read a cached objects from sql not need to run again.

Other trick: order by Date asc if you have huge result, than better, faster to do it in PHP side, those can rally slow down the query if they need to do a full table scan.

Other like Yannik told: pagination ( this is basic, ofc ) and divide pages.

You can speed up the delay from pagination with pre-executing sql with Ajax: get count of total results for pagination.

Yes, obviously if you have a lot of queries on a single page then even in moderate traffic it can flood your database with queries.

Few Tips: 1)You should work on your database structure,how you have created tables,which table stores what,normalization etc.Try to optimise storage and retrieval of information so that in a single query,you fetch max. information.This will reduce the calls to database.

2)Never store and fetch redundant info (like age,that you can calculate from DOB) from database.

3)Pagination (as pointed earlier).

4)Caching

5)If you are updating small portions on your page at a time,then instead of loading entire page,use AJAX to update necessary portions.It will also increase interactivity.