» Find Revision
L2J Revision Number:2856
L2JDP Revision Number:5862
Hello guys, i have 1 dedicated server with the following configuration:
Intel Core2 Quad Q9300
8GB Ram DDR2
2 VelociRaptors 10K RPM
Windows 2003 Standard x64
JDK 1.6.0_13 x64
MySQL 5.1.33 x64
Link 100 Mbps
I need some help in setting up, because some players are experiencing lag(players average: 150 online), and I do not know if my setup is right:
startGameServer.bat:
Code: Select all
java -server -Xmx6114m -Xms6114m -XX:PermSize=256m -XX:SurvivorRatio=8 -XX:+UseParallelGC -XX:+AggressiveOpts -XX:NewRatio=3 -cp ./../libs/*;l2jserver.jar net.sf.l2j.gameserver.GameServerCode: 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 # Packet LifeTime in milliseconds. Disabled = 0.# Default: 0PacketLifeTime = 0 # 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 # ---------------------------------------------------------------------------# Optimization# ---------------------------------------------------------------------------# Flood Protector. Set the initial size of the flood protector (should equal about roughly your player count)# Default: 50FloodProtectorInitialSize = 300 # Items on ground management.# Allow players to drop items on the ground.# Default: TrueAllowDiscardItem = false # Delete dropped reward items from world after a specified amount of seconds. Disabled = 0.# Default: 0AutoDestroyDroppedItemAfter = 90 # Time in secs after which dropped herb will be auto-destroyed (default: 15 seconds)# Default: 15AutoDestroyHerbTime = 15 # List of items that will not be destroyed (separated by ",").# Notes:# Make sure the lists do NOT CONTAIN trailing spaces or spaces between the numbers!# Items on this list will be protected regardless of the following options.# Default: 57,5575,6673ListOfProtectedItems = 5575 # This is the interval (in minutes), that the gameserver will update a players information such as location.# The higher you set this number, there will be less character information saving so you will have less accessessing of the database and your hard drive(s).# The lower you set this number, there will be more frequent character information saving so you will have more access to the database and your hard drive(s).# A value of 0 disables periodic saving.# Independent of this setting the character is always saved after leaving the world.# Default: 15CharacterDataStoreInterval = 1 # This enables the server to only update items when saving the character.# Enabling this greatly reduces DB usage and improves performance.# WARNING: This option causes item loss during crashes.# Default: FalseLazyItemsUpdate = True # When enabled, this forces (even if using lazy item updates) the items owned by the character to be updated into DB when saving its character.# Default: FalseUpdateItemsOnCharStore = True # Also delete from world misc. items dropped by players (all except equip-able items).# Notes:# Works only if AutoDestroyDroppedItemAfter is greater than 0.# Default: FalseDestroyPlayerDroppedItem = True # Destroy dropped equipable items (armor, weapon, jewelry).# Notes:# Works only if DestroyPlayerDroppedItem = True# Default: FalseDestroyEquipableItem = True # Save dropped items into the database for restoring after restart.# Default: FalseSaveDroppedItem = False # Enable/Disable the emptying of the stored dropped items table after items are loaded into memory (safety setting).# If the server crashed before saving items, on next start old items will be restored and players may already have picked up some of them so this will prevent duplicates.# Default: FalseEmptyDroppedItemTableAfterLoad = False # Time interval in minutes to save in DB items on ground. Disabled = 0.# Notes:# If SaveDroppedItemInterval is disabled, items will be saved into the database only at server shutdown.# Default: 60SaveDroppedItemInterval = 0 # Delete all saved items from the database on next restart?# Notes:# Works only if SaveDroppedItem = False.# Default: FalseClearDroppedItemTable = False # Delete invalid quest from players.# Default: FalseAutoDeleteInvalidQuestData = False # Setting False can improve server performance on high rate/population servers.# Default: TruePreciseDropCalculation = False # Allow creating multiple non-stackable items at one time?# Default: TrueMultipleItemDrop = True # Forces full item inventory packet to be sent for any item change.# Notes:# This can increase network traffic # Default: FalseForceInventoryUpdate = False # True = Load html's into cache only on first time html is requested.# False = Load all html's into cache on server startup.# Default: TrueLazyCache = True # Minimum and maximum variables in seconds for npc animation delay.# You must keep MinNPCAnimation < = MaxNPCAnimation.# Default: 10MinNPCAnimation = 0 # Default: 20MaxNPCAnimation = 0 # Default: 5MinMonsterAnimation = 0 # Default: 20MaxMonsterAnimation = 0 # Knownlist (the list of things a character sees) update method. Default is currently time based updating, which also makes it possible to use config options for guards to see moving monsters. Alternatively move based update can be used but guards cannot track mobs with that option but otherwise it should work well.# Default: FalseMoveBasedKnownlist = False # Interval (in miliseconds) in which the knownlist does full updates.# For move based updates its used for intermediate updates.# WARNING!# Useful interval is between 300 - 2000. Too small value may kill your CPU, too high value may not update knownlists properly. The default value is chosen experimentally.# Default: 1250KnownListUpdateInterval = 1250 # Grid options: Grids can turn themselves on and off. This also affects the loading and processing of all AI tasks and (in the future) geodata within this grid.# Turn on for a grid with a person in it is immediate, but it then turns on the 8 neighboring grids based on the specified number of seconds.# Turn off for a grid and neighbors occurs after the specified number of seconds have passed during which a grid has had no players in or in any of its neighbors.# The always on option allows to ignore all this and let all grids be active at all times (not suggested).# Default: FalseGridsAlwaysOn = False # Default: 1GridNeighborTurnOnTime = 1 # Default: 90GridNeighborTurnOffTime = 90 # ---------------------------------------------------------------------------# Geodata# ---------------------------------------------------------------------------# GeoData options:# 0 = GeoData and PathFinding OFF (default)# 1 = GeoData is used to check Line Of Sight (LOS) targeting and # L2Playable movement. You need to download files for data/geodata folder.# Monsters can pass walls but not aggro (no line of sight) through them.# 2 = Full GeoData enabled. Includes PathFinding (requires also /data/pathnode # files if CellPathFinding not enabled) and all character moves go through # geodata checks (if a mob passes a wall, pathfinding didn't find a route # but we allow attack and returning home).# Recommended server memory minimum 2 GB, rather 3 GB.# Default: 0GeoData = 1 # Cell-level pathfinding, produces more accurate routes but is (maybe 10x) heavier to calculate. Recommended for small servers at least.# If False, pathnode files are used. Uses a max number of nodes in calculation which can be adjusted in the algorithm if it needs to be faster.# Default: FalseCellPathFinding = False # True = Loads GeoData buffer's content into physical memory.# False = Does not necessarily imply that the GeoData buffer's content is not resident in physical memory.# Default: TrueForceGeodata = True # This setting controls Client <--> Server Player coordinates synchronization:# -1 - Will synchronize only Z from Client --> Server. Default when no geodata.# 1 - Synchronization Client --> Server only. Using this option (without geodata) makes it more difficult for players to bypass obstacles.# 2 - Intended for geodata (at least with cell-level pathfinding, otherwise can you try -1).# Server sends validation packet if client goes too far from server calculated coordinates.# Default: -1CoordSynchronize = 1Code: Select all
# MySQL Server Instance Configuration File# ----------------------------------------------------------------------# Generated by the MySQL Server Instance Configuration Wizard### Installation Instructions# ----------------------------------------------------------------------## On Linux you can copy this file to /etc/my.cnf to set global options,# mysql-data-dir/my.cnf to set server-specific options# (@localstatedir@ for this installation) or to# ~/.my.cnf to set user-specific options.## On Windows you should keep this file in the installation directory # of your server (e.g. C:\Program Files\MySQL\MySQL Server X.Y). To# make sure the server reads the config file use the startup option # "--defaults-file". ## To run run the server from the command line, execute this in a # command line shell, e.g.# mysqld --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"## To install the server as a Windows service manually, execute this in a # command line shell, e.g.# mysqld --install MySQLXY --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"## And then execute this in a command line shell to start the server, e.g.# net start MySQLXY### Guildlines for editing this file# ----------------------------------------------------------------------## In this file, you can use all long options that the program supports.# If you want to know the options a program supports, start the program# with the "--help" option.## More detailed information about the individual options can also be# found in the manual.### CLIENT SECTION# ----------------------------------------------------------------------## The following options will be read by MySQL client applications.# Note that only client applications shipped by MySQL are guaranteed# to read this section. If you want your own MySQL client program to# honor these values, you need to specify it as an option during the# MySQL client library initialization.#[client] port=3306 [mysql] default-character-set=latin1 # 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.1/" #Path to the database rootdatadir="C:/Documents and Settings/All Users/Application Data/MySQL/MySQL Server 5.1/Data/" # The default character set that will be used when a new schema or table is# created and no character set is defineddefault-character-set=latin1 # The default storage engine that will be used when create new tables whendefault-storage-engine=INNODB # 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=600 # 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=2000 # 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=256M # 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=45 #*** 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_max_extra_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=64M # 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=384M # 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 ***innodb_data_home_dir="D:/MySQL Datafiles/" # 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=8M # 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=2 # 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=16M # 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=1024M # 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=512M # 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=60 #Lock mysqld in memory.(=Don't swap.)memlock
