Hi,

I've got UBB.classic 6.3.1.1, and am having problems with the CPU maxing out for seconds at a time. The board currently has 2,998 registered users, and 336,642 posts on 14 forums. I'm not sure what is causing the server to run slowly, but I'm sure the cause is the UBB, since it's the perl executable that is using the CPU. (And the rest of the site uses ASP.) Am I overloading UBB.classic, and would switching to UBB.threads fix the problem? I've tried running the maintenance options on the board, and they usually fix the problem for a month or so, but it seems to be getting worse. Assuming the answer is yes, I have a few questions about the new version:

1) Is there a style/theme/etc that will keep the look of the bulletin board similar to the default UBB.classic 6.3.1.1 look I had before?
2) Will URL links to old posts still work, or if not, is there a way to patch this?
3) I have EMC Retrospect backup software that makes a copy of the changes to the inetpub directory daily; is there a simple way for it to backup the MySQL/etc data files?
4) How much would it cost to upgrade, including installation?
5) How do you remotely install the software? I'm running Win2K; Terminal Services client?
6) Does the new version support 'sticky posts'? (The only feature we're missing!)

Note that I do not currently have MySQL installed, and am running ActiveState ActivePerl v5.6.

I'm not posting my license key here for security purposes, but you can find it under my email address, which I used to register on this board with. (I do have my license key, if you'd like me to email it to you.) The bulletin board requires an invitation, so you can't view it now, but I'd be happy to email you a name & password if you need to see the board in action.

You can check out the website at www.raisinggodlytomatoes.com.

Thanks,

Shane

FWIW - My Classic 6.7.2 had 4534 users, 15 forums, 335k posts on a shared server and didn't run into any problems.

would switching to UBB.threads fix the problem?

Threads 7 should be more server-friendly as it uses a database rather than flat files to store all the data. However, I'm not certain that is your problem. Are you on a shared server like I am?

1) Is there a style/theme/etc that will keep the look of the bulletin board similar to the default UBB.classic 6.3.1.1 look I had before?

Threads 7 uses a style system that helps you create any look you could possibly imagine for a forum.

2) Will URL links to old posts still work, or if not, is there a way to patch this?

After importing all your Classic data into Threads, you can then very easily install re-directors to redirect from the old posts to the new posts.

3) I have EMC Retrospect backup software that makes a copy of the changes to the inetpub directory daily; is there a simple way for it to backup the MySQL/etc data files?

Others would know better than I would, but it should be as simple as adding a cron job to backup your files and database.

4) How much would it cost to upgrade, including installation?

Rick would have to answer that, after gaining access to your forums. You will first have to upgrade to Classic 6.7.* before upgrading to Threads 7.*

5) How do you remotely install the software? I'm running Win2K; Terminal Services client?

Installation is simply a matter of FTP'ing the files, setting file permissions, then running a web-based install script.

6) Does the new version support 'sticky posts'? (The only feature we're missing!)

Yes, Sir. This feature was added in a later version of Classic actually.

Note that I do not currently have MySQL installed, and am running ActiveState ActivePerl v5.6.

I'm unfamiliar w/ that environment, but you will certainly need MySQL and PHP installed. You can look at the Documentation to see which minimal versions you'll need.

It's a dedicated server, and there's nothing else on the server that uses perl or bogs the CPU. It's searches, usually, that bog down the server. I just now ran a test search; memory usage rose 130MB, and it took over 3 minutes to complete, with CPU usage at 100% for the duration. Normally the CPU will idle; spiking every few seconds to maybe 50%.

I'd be willing to beleive that classic is the cu;prit, larger installs can be intensive on any server.

MySQL however will be a nessessity, you'll have to install it before running UBB.T.

Upgrading to ubb.classic 6.7.3 itself will help tremendously with the server load, Charles did a lot of work making classic much easier on the server during te 6.5-6.7 versions. If you are running a dedicated server it should be able to run classic for a while unless you have *lots* of posting/searching going on - even then the quick reply and some improvements in the search function in the 6.6+ versions will help there. Don't allow searching of all forums for one (hard on any largish forum, php/mysql or flat-file ).

Oh, install more recent versions of active state's perl too, many improvements in the code and the upgrade is a free one

Having said all that, threads is where you'll need to move at some point, tho you can extend the life of your current setup if you'll just upgrade to 6.7.3, upgrade perl and php on your server.

Using the php accelerator with 6.7.3 (built-in) will make an amazing difference in the speed of your site too

I miss charles whining that Perl is better than php hehe

None of that is going to fix the search all that much. Yes Charles optimized it as best he could in later versions, but yes, it's still a flat file based system using a flat file based search containing over 300 thousand posts.

Best thing you can do is install php and mysql, then move to threads.

Don't, however, think you're going to move to threads and everything will be honey and roses. You WILL need to spend some time tuning your MySQL installation after you import and go live. Especially being on a Windows box. An untuned MySQL is hit or miss as to whether it runs well. A properly tuned MySQL will run smooth and fast, extend the live of your server immeasurably and will put a big smile on your face.

It was more the idea if the current server is doing 'ok' then adding the php accelerator and various other improvements will make a very nice addition to speed.

Good point, Allen, and you're right.