Server becomes laggy after some time?

09/29/2011 11:51 Svinseladden#1
mabe bad title but well when times goes by the server get's bigger and bigger. and use more and more ram of the server. the ram get'sa insane after a day or 2 running it. and yes i know i can restart the sql. But is there anything ppl do each maint or something? like what's happening if you remove the log each maint? that's just what happend right? have it in backup or something for a week or 2. or does that effect the game in any way?

os do all just keep everything as it is? i belive the server get's more and more laggy each week. or is that me?

thanks for every answer out there from ppl that have more time of running the server
09/30/2011 03:23 ·Tyler·#2
Restart the host, it helps. :)

Tyler
09/30/2011 07:43 Svinseladden#3
Quote:
Originally Posted by ·Tyler· View Post
Restart the host, it helps. :)

Tyler
hahahah well i do that each maint. but not everyday..
09/30/2011 22:05 -III-#4
You are right, it does seem that over time, latency issues build to higher amounts. What I have found that helps is the following:

-Keep your action log tidy (personally, I delete everything older than 30 days once a month)

-Keep your chat log minimal (again, I delete everything older than 30 days once a month)

-Be sure to restart the physical machine each time you do maintenance

-Delete all traces of toons from permanently banned accounts. Char inventory, auction house, friends lists, guild lists, etc...

-Remove inactive accounts. Be sure to remember account warehouses as well.

Over time, you can amass needless database records from accounts that haven't logged in for months at a time, as well as junk left behind from banned accounts. Chat logs and action logs are the biggest culprits behind demanding mass database space.

Keeping these aspect in check will help with your server performance greatly. After all, a database is like a big box full of junk. If at any time you wish to find one specific item, you have to sort through all of it before finding it.

The less you have to sort through, the quicker you'll find it.

There are significantly more aspects to list, but these are quick and easy.

I would also suggest keeping your web server on a different machine, if feasible. The lag wont always be due to the machine, but rather the network. A web server is a prime target for many people who are just looking to be a pain in the ass.

If your webserver becomes a target, and it is stored on the same server as your game/database servers, the strain from one will effect all.

The same applies to your databases as well. The nice thing about the server setup files is that you have to option to input an IP address for each database. This means you can host them separately as well, thus spreading the strain to more than one resource.

However, this can be quite expensive if you do not have the means to host everything yourself. However, it is an option, nonetheless.

The biggest thing to focus on is housekeeping. The better organized and tidy your server is, the better it will perform. You can also use a few analytic programs if need be to search out bottlenecks and flawed server mechanics.

-III
Shaiya Absolution
09/30/2011 22:50 Svinseladden#5
thanks alot. anyone should come up with server cleaner:-) remove everything with a date. like sql remove everything in chatlog and gamelog above 30 day's or something like that. would be a great litle thingy.

and ok 30 day's that's the normal cleaning date:-P

thanks

what i normaly use is:

delete
from <PS_GameLog>
where ActionTime is <= getdate() - 30

and

delete
from <PS_Chatlog>
where ChatTime is <= getdate() - 30
10/07/2011 09:58 Svinseladden#6
i have done a 30 day clean up. ok not chars/charsitems and accounts but out of the blue ppl now need to put in there password 2 times to get in. anyone hade that one before? could a reinstall if sql work? or is this just how it get's? sql in the logg now have million's of line's. and we have insanly many accounts created and then chars made. but i have seen servers with alot more then on mine, still work normal. so ppl have to have solved this before? i'm using sql 2008r2 btw