Yes Sachin, Now DP upgraded to 3.6.12 from 3.6.8. I also like changes made today as forum once again working smooth and fast same as we used in past.
This is a pretty epic return by Shawn. I hope it will end the progessive decline of DP (server issues, helpless mods) as it seems no one has had the power to change anything.
can removing the members' list make a significant difference to my 4000 member forum? of course, DP has a large user base, but then my forum is running on a shared host.
Yes it would be a tedious task, and does appear Shawn of Digitalpoint has got the site running faster and the images where never an issue. But There are more better suited applications out there for serving static content like Varnish, Squid, Nginx and Lighthttpd. But examine Apache's memory footprint. If you serve images with Apache. Apache can easily consume 15MB RAM per httpd process. So you have someone come and grab 30 images off the page. They will start opening and closing 30 httpd processes (since Apache is a threaded application). So Is serving a 1KB 16x16 image worth 15MB of ram on your server? No probably not. Also if your Keep-Alive is set to the default 300 seconds they will hog one Max client slot for 5 minutes. (Each idle maxclient requires RAM). If your running a website and it starts getting more popular and your serving hundreds of images a second with apache, you can easily end up in a situation where you run out of Max clients and RAM, and you have to start spending a bunch of money upgrading your server's with tons of RAM and other expensive hardware.
DP surely uses a lot of Ram. Nginx reduces the Ram load on the server drastically. Apache eats your ram!!!! Nginx does make the site load faster than when its used on apache. I removed apache long back and installed nginx and I'm surprised. Nginx is way better than apache. We can further reduce load by removing : - Similar threads feature at bottom of threads and the last post feature in profiles. PS - Xcache is awesome,
Well, as I said... Apache (or static content) was never (ever) an issue here. The most overloaded Apache process at the moment is consuming 0.001% of the server's memory. Also, KeepAliveTimeout forces people to use the same httpd process for all their requests. And yes, I'm also quite aware a Timeout of 300 on a busy server is horrible. It's never been set anywhere remotely that high since day one. /sigh... see every one of my previous posts in this thread... Apache is not (and never was) the bottleneck for this site. The web servers for this site pretty much sit around idle doing nothing compared to the other servers.