I've got a rapidly growing photopost installation - 12k photos, growing at a rate of about 2-3k per month lately. We've got multiple hundreds of categories and 50-100 concurrent users throughout the day, about 120k page views/day in the gallery. my poor server simply cannot handle the load and I've got database guys telling me that photopost "doesn't scale well". we've already optimized the indexing, I moved to a dedicated server a couple months ago and had hopes that this would solve my performance problems. Do I really need to pay $500+ per month (the going rate at my provider) to upgrade to a high-end machine and fast drives to host my not-so-large site? what can I do to improve performance?
I'm desperate at this point and would love to hear any ideas from those who've been through this. what about something like Turck MMCache? should I look for a different provider in hopes of getting a better deal somewhere else? can I optimize pp somehow? tia
While I don't have that large of a PP install, I do have a fairly active vBulletin with 80K page views per day. My PP install gets about 10K page views per day with a few smaller sites for an additional 10K. At this time I have to run a dedicated 2.4G Pentium with 1G RAM to stay ahead of any problems. I figure I can about double my visits before I will need to upgrade. So yes, I figure with 120K page views you will need a fairly powerful server to run it. I do have PHPA installed to help speed up things.
Looks like you are running a 1.6G Pentium and hopefully you have more then the standard 256M RAM. Upgrading the RAM to 1G would help a LOT!
Last edited by HobbyTalk; July 6th, 2004 at 11:27 PM.
my understanding is that the differences in 4.8 are only indexing. I've already upgraded, and gone through some indexing exercises, with minimal improvements. I *really* need to see my questions addressed more seriously by some support people here. what can be done to improve performance of photopost on active sites?
please answer this question: should I expect to have to run photopost on a high-performance dedicated server if my site gets busy?
thanks, I'll try turning off the who's online, and also your other suggestions, though I hate the idea of having to disable features in order to keep my server from toppling over. my question still stands though, what kind of hardware requirements should I expect when running a fairly active pp site? is it the norm to *not* be able to run pp in a typical shared-hosting kind of setup? I'm having to throw all kinds of hardware and $$ at the problem in hopes of keeping my site alive, is this the norm?
Well most people run Photopost in a shared environment.
However there are user's who have larger sites with a fair amount of traffic. These sites need dedicated servers. No way around that. How many GB a month traffic do you do?
The things you want to look for are price versus features obviously. Dedicated Servers can be expensive but once a site outgrows the shared environment thats it it is time.
I've got a rapidly growing photopost installation - 12k photos, growing at a rate of about 2-3k per month lately. We've got multiple hundreds of categories and 50-100 concurrent users throughout the day, about 120k page views/day in the gallery.
This tells me your most likely read for a dedicated server if your still on a shared plan. Problem is your site really from a user standpoint is not big. However if you have 100 users online at the same time all requesting page views that most likely the load on the server is going through the roof for mysql queries You might try to also tweak your mysql
I *used* to be on a shared plan, I just never dreamed that a dedicated server would be in my future. and now that I'm on a 2.4 ghz dedicated box, that I figured would solve every problem I've ever had, and it's toppling over on a daily basis, I'm just a little distressed and frustrated. we have over 100 concurrent users regularly and I believe we're doing 120-150 GB a month, most all of which is PP. I love photopost but it bothers me greatly that my members are having to put up with these issues.
More than likely your apache and mysql have to be configured and tweaked a bit. I would first go setting your mysql settings to the larger database norms for mysql. They have some examples at mysql.com for larger sites
Your server logs and such should give you some hints on exactly what is bogging things down so that would be best to look into