- Reaction score
- 198
- Points
- 1,210
It'll be no surprise to anyone here that I've been an absentee admin for Afghan Ops in recent months. I've been slow to respond to reported problems, feature requests have tapered off sharply and heck - even April fools came and went with no clowns this year. Truth be told, I've been tied up with a growing list of other commitments. Unfortunately this means AO has taken a back seat, with no new content to draw people in to play. That, in turn has lead to a lack of MilPoints purchases - nobody wants to play a game that has all but dried up, so there has been no purchases since Sept 2012. In a predictable cycle, I've been trying to focus on projects that have a return on my time causing AO to slip further down my list. I realize at this point it's starting to sound like a plea for cash, but that's really not it so I'll get to the point.
One of the things I have been fighting recently is an insidious performance problem on the server. At seemingly random times, there's a resource spike and the server shuts down, sometimes coming back automatically, sometimes not. Early this morning, I traced that spike to AO.
Sure this is a problem, but it's amplified by the fact that over the last few months some of the other projects I've been working on have included paying customers who have their data and sites hosted on our server. Yesterday's outage hit one project particularly hard and caused ripple effects on several other services on their end. I'm now in the unfortunate situation where AO is impacting other paid projects I have on the go, and I have to make a decision.
Possible solutions include:
Cheers and thanks
Mike
One of the things I have been fighting recently is an insidious performance problem on the server. At seemingly random times, there's a resource spike and the server shuts down, sometimes coming back automatically, sometimes not. Early this morning, I traced that spike to AO.
Sure this is a problem, but it's amplified by the fact that over the last few months some of the other projects I've been working on have included paying customers who have their data and sites hosted on our server. Yesterday's outage hit one project particularly hard and caused ripple effects on several other services on their end. I'm now in the unfortunate situation where AO is impacting other paid projects I have on the go, and I have to make a decision.
Possible solutions include:
- Solve the problem. Yep, that's the obvious answer, but it's not as simple as that unfortunately. The problem is likely inefficient coding, poor database design, server settings that are slightly off spec or (likely) all of the above. Finding those, let alone fixing those is a big task that will take significant time and effort. As noted above, I don't really have a lot of spare cycles to throw at the problem and waiting means putting my other projects in jeopardy until I can get around to it.
- Trim back the game. Spend some time to find out where the inefficiencies are (E.G. equipment proficiency levels) and cut those out of the game. This would be difficult to do without tipping the balance, and may not ultimately solve the problem if I can't find the problem source.
- Get a bigger server. Certainly a consideration, but if the paid projects don't require me to bump up our hosting plan, it seems counter-intuitive to do it for an unpaid project. And there's nothing to say we won't immediately hit the same performance wall again. (See the bit about inefficient coding above. )
- Shut down AO. Not my top choice by a long stretch, but it resolves the performance issue immediately and doesn't put a funding source in jeopardy. I see this as a last resort only. In fact, I will fight this one to the end. AO is still my baby, even though I neglect it.
Cheers and thanks
Mike