Photopost 5.0.3 server resource questions
 

I have a site running Photopost 5.0.3 and I was wondering if any server resource hoging bugs were fixed between 5.0.3 and 5.14?

I have a dual 2.8Ghz Xeon box with 1GB of memory and my gallery usually has 30 people on constantly throughout the day, but it can spike to 60 - 90 users. The only other real intensive site I have on the box is a VB 3.0.7 forum that that normally has between 200 - 300 users.

I didn't think that a forum this small and only this few of people on my photopost site would cause problems with a box as powerful as this, but the host is telling me that it is and are trying to swaying me to get another 1Gb sick of ram for a monthly charge of $50 a month or a one time fee of $400.

Does anybody know any solutions or have had similar problems trying to grow their galleries popularity? Anybody that can provide any info or pointers they would greatly appreciated. If there's a way I can save money I would really like to know about it.

Thank you!

VB is a resource hog but as far as Photopost is concerned I would definately upgrade as the code is less intensive

less intensive by a small bit or a good deal? Since I like to really customize my photopost installs I'm just wondering if it's going to really change the fact that I am going to probably have to fork over money for that 1GB stick. :\

well lots and lots of code changes from 5.03 to 5.14

I have just about the same number users but only about 10 people on-line on my PP. Considering I only have a 2.4 Celeron and 1G RAM my server still easily handles the load with less then .6 load almost all the time. While upgrading to the lastest versions is always recommended I would suspect your server could be better optimized for php/myqsl.

You may also want to disable some of the optional more server intensive operations on vB such as displaying Current Active Users on main pages, Birthdays, etc.

Yep and when VB 3.5 goes gold you should upgrade as its alot faster than VB 3.0

Thanks for the info, I will try turning off some of those features you mentioned. I will unlikely upgrade to vb3.5 as I've already tweaked 3.0.7 up the ***. If I woulda known 3.5 was a great deal faster maybe I would have held off on some of the modifications, but the upgrade to 3.0.7 was a must from my old 2.0.3 maybe when 4.0.3+ comes out I can upgrade again. ;)