It’s not me who is writing irrelevant posts all the time. I am merely the person who is disagreeing with these posts of you, so stop accusing me of thinking that I am the smartest person here if you can’t back that up.
Sure, a site with relatively low traffic is fine for 128kbps. But you only need three or more people in the evening to open a page at the same time and the speed of each one of them will go down. Offering larger images or even downloads would make 128kpbs totally unfeasible for websites.
With http includes they mean using include() on a file which is located on a remote server. There is no difference when it comes to MySQL connections between include(‘bla’); or include(‘http://yoursite.com/bla’); if both pages are on your server.
bitbytes recommended using persistent connections when the MySQL server is a physically separate machine to your web server. The latency involved in connecting is greater because it’s over a network.
It doesn’t mean permanent connections are right for a single-server site.
Hosting a web server at home isn’t very sensible (the reasons have been covered in the web hosting forum many many times but to reiterate - bandwidth, latency, hardware and 24/7 energy costs, security, 24/7/365 service, consistency are all negatively affected by hosting at home. It’s actually more expensive than most normal shared hosting once you factor in all costs).
If you’re unable to use a better host (the simple solution) then you may be able to implement a cache system with any data that doesn’t update too frequently to avoid performing a query.
Get age of cache file, If still fresh - load and use data, else perform query and write new data.
This way you can decimate the amount of queries made albeit with increased file access overhead.