I have a Core 2 Quad Q9550, 8GB DDR2 RAM, 250GB SATAII, 100MBPS UP / DOWN, Windows Server 2003 64bit, Navicat 8, Java 6 JDK 64, Mysql 64.
I'm too lag, a few days now the server started to lag.
I need help, what do you advise me to do about it?
L2jServer Epilogue, 400/500 Players Online.
Server Lag, i need help.
Forum rules
READ NOW: L2j Forums Rules of Conduct
READ NOW: L2j Forums Rules of Conduct
-
- Posts: 276
- Joined: Wed Apr 15, 2009 6:41 am
Re: Server Lag, i need help.
For anyone to help you, you will have to post more information then that, your mysql settings, the information in your gameserver.bat, your thread configuration settings.
-
- Posts: 183
- Joined: Thu Jul 15, 2010 12:26 am
Re: Server Lag, i need help.
StartGameServer.bat
Thread Configuration
Mysql Config.
Code: Select all
@echo offtitle Game Server Console:startecho Starting L2J Game Server.echo.REM -------------------------------------REM Default parameters for a basic server.REM java -Djava.util.logging.manager=com.l2jserver.util.L2LogManager -Xms4024m -Xmx6024m -cp ./../libs/*;l2jserver.jar com.l2jserver.gameserver.GameServerREMREM If you have a big server and lots of memory, you could experiment for example withREM java -server -Xmx1536m -Xms1024m -Xmn512m -XX:PermSize=256m -XX:SurvivorRatio=8 -Xnoclassgc -XX:+AggressiveOptsREM If you are having troubles on server shutdown (saving data),REM add this to startup paramethers: -Djava.util.logging.manager=com.l2jserver.L2LogManager. Example:java -Djava.util.logging.manager=com.l2jserver.util.L2LogManager -Xmx6144m -cp ./../libs/*;l2jserver.jar com.l2jserver.gameserver.GameServerREM -------------------------------------if ERRORLEVEL 2 goto restartif ERRORLEVEL 1 goto errorgoto end:restartecho.echo Admin Restart ...echo.goto start:errorecho.echo Server terminated abnormalyecho.:endecho.echo server terminatedecho.pause
Thread Configuration
Code: Select all
# ---------------------------------------------------------------------------# Thread Configuration# ---------------------------------------------------------------------------# Extreme caution should be here, set to defaults if you do not know what you are doing.# These could possibly hurt your servers performance or improve it depending on your server's configuration, size, and other factors.# Default: 10ThreadPoolSizeEffects = 50 # Default: 13ThreadPoolSizeGeneral = 65 # Default: 2UrgentPacketThreadCoreSize = 10 # Default: 4GeneralPacketThreadCoreSize = 20 # Default: 4GeneralThreadCoreSize = 20 # Default: 6AiMaxThread = 20 # Dead Lock Detector (a separate thread for detecting deadlocks).# For improved crash logs and automatic restart in deadlock case if enabled.# Check interval is in seconds.# Default: FalseDeadLockDetector = False # Default: 20DeadLockCheckInterval = 20 # Default: FalseRestartOnDeadlock = False
Code: Select all
# SERVER SECTION# ----------------------------------------------------------------------## The following options will be read by the MySQL Server. Make sure that# you have installed the server correctly (see above) so it reads this # file.#[mysqld] # The TCP/IP Port the MySQL Server will listen onport=3306 #Path to installation directory. All paths are usually resolved relative to this.basedir="C:/Program Files/MySQL/MySQL Server 5.5/" #Path to the database rootdatadir="C:/ProgramData/MySQL/MySQL Server 5.5/Data/" # The default character set that will be used when a new schema or table is# created and no character set is definedcharacter-set-server=latin1 # The default storage engine that will be used when create new tables when#default-storage-engine=INNODB # Set the SQL mode to strictsql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION" # The maximum amount of concurrent sessions the MySQL server will# allow. One of these connections will be reserved for a user with# SUPER privileges to allow the administrator to login even if the# connection limit has been reached.max_connections=100000 # Query cache is used to cache SELECT results and later return them# without actual executing the same query once again. Having the query# cache enabled may result in significant speed improvements, if your# have a lot of identical queries and rarely changing tables. See the# "Qcache_lowmem_prunes" status variable to check if the current value# is high enough for your load.# Note: In case your tables change very often or if your queries are# textually different every time, the query cache may result in a# slowdown instead of a performance improvement.query_cache_size=0 # The number of open tables for all threads. Increasing this value# increases the number of file descriptors that mysqld requires.# Therefore you have to make sure to set the amount of open files# allowed to at least 4096 in the variable "open-files-limit" in# section [mysqld_safe]table_cache=256 # Maximum size for internal (in-memory) temporary tables. If a table# grows larger than this value, it is automatically converted to disk# based table This limitation is for a single table. There can be many# of them.tmp_table_size=205M # How many threads we should keep in a cache for reuse. When a client# disconnects, the client's threads are put in the cache if there aren't# more than thread_cache_size threads from before. This greatly reduces# the amount of thread creations needed if you have a lot of new# connections. (Normally this doesn't give a notable performance# improvement if you have a good thread implementation.)thread_cache_size=8 #*** MyISAM Specific options # The maximum size of the temporary file MySQL is allowed to use while# recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.# If the file-size would be bigger than this, the index will be created# through the key cache (which is slower).myisam_max_sort_file_size=100G # If the temporary file used for fast index creation would be bigger# than using the key cache by the amount specified here, then prefer the# key cache method. This is mainly used to force long character keys in# large tables to use the slower key cache method to create the index.myisam_sort_buffer_size=410M # Size of the Key Buffer, used to cache index blocks for MyISAM tables.# Do not set it larger than 30% of your available memory, as some memory# is also required by the OS to cache rows. Even if you're not using# MyISAM tables, you should still set it to 8-64M as it will also be# used for internal temporary disk tables.key_buffer_size=354M # Size of the buffer used for doing full table scans of MyISAM tables.# Allocated per thread, if a full scan is needed.read_buffer_size=64Kread_rnd_buffer_size=256K # This buffer is allocated when MySQL needs to rebuild the index in# REPAIR, OPTIMZE, ALTER table statements as well as in LOAD DATA INFILE# into an empty table. It is allocated per thread so be careful with# large settings.sort_buffer_size=256K #*** INNODB Specific options *** # Use this option if you have a MySQL server with InnoDB support enabled# but you do not plan to use it. This will save memory and disk space# and speed up some things.#skip-innodb # Additional memory pool that is used by InnoDB to store metadata# information. If InnoDB requires more memory for this purpose it will# start to allocate it from the OS. As this is fast enough on most# recent operating systems, you normally do not need to change this# value. SHOW INNODB STATUS will display the current amount used.innodb_additional_mem_pool_size=15M # If set to 1, InnoDB will flush (fsync) the transaction logs to the# disk at each commit, which offers full ACID behavior. If you are# willing to compromise this safety, and you are running small# transactions, you may set this to 0 or 2 to reduce disk I/O to the# logs. Value 0 means that the log is only written to the log file and# the log file flushed to disk approximately once per second. Value 2# means the log is written to the log file at each commit, but the log# file is only flushed to disk approximately once per second.innodb_flush_log_at_trx_commit=1 # The size of the buffer InnoDB uses for buffering log data. As soon as# it is full, InnoDB will have to flush it to disk. As it is flushed# once per second anyway, it does not make sense to have it very large# (even with long transactions).innodb_log_buffer_size=7M # InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and# row data. The bigger you set this the less disk I/O is needed to# access data in tables. On a dedicated database server you may set this# parameter up to 80% of the machine physical memory size. Do not set it# too large, though, because competition of the physical memory may# cause paging in the operating system. Note that on 32bit systems you# might be limited to 2-3.5G of user level memory per process, so do not# set it too high.innodb_buffer_pool_size=686M # Size of each log file in a log group. You should set the combined size# of log files to about 25%-100% of your buffer pool size to avoid# unneeded buffer pool flush activity on log file overwrite. However,# note that a larger logfile size will increase the time needed for the# recovery process.innodb_log_file_size=343M # Number of threads allowed inside the InnoDB kernel. The optimal value# depends highly on the application, hardware as well as the OS# scheduler properties. A too high value may lead to thread thrashing.innodb_thread_concurrency=8
-
- Posts: 458
- Joined: Fri Oct 05, 2007 1:29 am
Re: Server Lag, i need help.
try linux as OS, you lose to much ram for win... also try to configure mysql for 3gb rammaxstyleboy wrote:I have a Core 2 Quad Q9550, 8GB DDR2 RAM, 250GB SATAII, 100MBPS UP / DOWN, Windows Server 2003 64bit, Navicat 8, Java 6 JDK 64, Mysql 64.
I'm too lag, a few days now the server started to lag.
I need help, what do you advise me to do about it?
L2jServer Epilogue, 400/500 Players Online.