Keep our site running fast????

It's not up to the users to figure out what the problems are. The only thing we can do to help the process is report performance issues.

Like I said earlier... site's been running fast today... no glitches here. If you think that's whining, that's your problem.

 

Would archiving or deleting old threads help?

I am asking, brainstorming, it's not a trick question.

Shiva, I don't have any problems on other sites so don't think it's the netbook. @ the other person, I usually log out completely on leaving the site.

 

Yes. This is why mods close large threads after 500 replies. Too many large and popular threads can weigh the system down a lot.

 

But a lot of the closed threads are still visible. Would they not have to be deleted for that to be effective? I don't know the answer, I am asking if you do.

 

Yes Viv, it can help. As you see, I offered the idea a couple times previously.

But, simply archiving the old post, is not really a solution. The archives should be purged (IMO), to significantly help. And even at that, as the site grows, hardware upgrades will be necessary.

...are you sure that wasn't meant as a trick question?! LOL

Best wishes for the Holidays

 

Whatever it was, it wasn't addressed to you, Angrydrawers.

I don't think the threads I refer to are archived, that is the point. They're on the board, even if they are closed. One imagines they are still taking up as much memory as before and if anyone opens them, might slow the board down as they did before being closed. Some appear on the most read thread list at the foot of the board, people may still see and open them.

Why close them to speed the board up and then leave them on? If it would help, perhaps they should be deleted.

Edit] SMW don't kill me, I've just noticed one of those big threads is yours.

 

Not quite. The staff generally documents when there appears to be a problem and the site owner drops in the check on that as well as give us updates on actions taken to resolve the problems.

As noted I'm perhaps the worse person to talk to about the suspected site problems. I know the site moved to a much larger server and that the site owner suspects the problems are for several different possible reasons but doesn't believe its the server specifically. Beyond that it's pretty much Greek to me.

 

Well, right now it's good, so I have no complaints. Enjoy the moment.

 

You're not providing anyone a service but yourself. Every single error is automatically reported to the admin. This is standard practice. If an error happens it gets placed in a log that gives a much more detailed account of events than you could ever provide.

 

LOL @ standard practice. What are you, the internet mechanic?

 

I'm a web developer. So... yes?

 

And all web sites are the same, right? Don't tell us, dear, send a PM to the administrator. Maybe you can be of some help behind the scenes.

 

If they aren't logging their errors then they akin to mechanics who don't know how to change their oil.

 

We do know that every error is automatically input into a log. I don't believe slow response times are but actual database errors are.

 

Hahahahahaha!

I actually agree with you. Perhaps they can be archived for a determined amount of time (say 6 months), then purged completely.

Oh well, I'm sure everything will eventually line out.

 

If this were Slashdot, I would say, install Linux, because on Slashdot, that is the answer to all problems. Not knowing much about PHPbb, I would only guess that this is running on a version of Linux like CentOS and a recent MySQL/PHP combo. Maybe it needs more tubes.

 

27 minutes to load the homepage tonight. While I was waiting, ordered jeans from LLBean, paid my cell phone bill, checked in a politicalbuddies.com & answered PMs.... IT'S NOT MY CONNECTION AND IT'S NOT MY COMPUTER!!!

Seems to have gotten over the hump and is now responding. However, since the 'auto log' doesn't register slowdowns (and I haven't gotten a DB error)... for the record, from 6-7 pm, the site was useless.

This post is just for the record...

 

If the site doesn't load for me in 2 minutes or less, I turn the computer off and come back to it in a half hour or so. My old one used to slow down after awhile. I imagined it being tired and needing a sleep!

The problem is that many people don't have a problem with the site when others do. If the problem was the forum, then everyone would struggle to come online at that particular time. Its really hard to pinpoint where the problem is, and that's likely what is taking so long to fix it.

 

If it took me 27 min to load a page and the problem was consistent, I would vote with my feet. That being said, I don't know if I could get the pen to stay in between my toes while I mark the ballot .

 

I'm not an apha-geek which I've admitted in the past but I do use a Linux operating system and, as I've noted, I have very few problems with Political Forum. I wonder if that is the reason?

 

I haven't changed a thing... but the site seems to be working better. Maybe it healed itself???

 

I usually get at least one or two database errors each time I am on, but they never last any longer than 10-15 seconds or so.

 

Generally, if you try to pull up PF and it coughs up a database error, that's a server issue, there is NOTHING at the user end that affects that other than the basic interaction with the website.

If... actually I should say WHEN PF stutters, I naturally run off to check other sites. Usually, the other sites come up fine while PF just sits there and spins.

This is NOT a user issue. This is (*)(*)(*)(*) poor technical management. Perhaps a competent techie could clean the DB up a bit? I know the site likes to tout its 57,000 members even though there are probably only a few thousand active. Also, take a look at automated routines that put a strain on aging equipment as well as filters and sorts. It seems that the longer my post is, the more likely that PF is going to throw up an error.

 

You're mostly on at off-peak hours since this is a predominantly North American site.

 

Did you log the one we just had that lasted about 30-45 minutes?