Need help tweaking my.ini

Ask questions about dedicated servers here and we and other users will do our best to answer them. Please also refer to the self-help section for tutorials and answers to the most commonly asked questions.
Post Reply
DangerRuss
New to forums
New to forums
Posts: 5
https://www.youtube.com/channel/UC40BgXanDqOYoVCYFDSTfHA
Joined: Sat Aug 29, 2015 2:21 pm

Need help tweaking my.ini

Post by DangerRuss »

So Im renting the

Four core
Four full, dedicated HT CPU cores (Nehalem or better)
4096 MB of RAM
400 GB of RAID-protected storage
16000 GB of bandwidth transfer

option VDS and Im running an Arma 2 OA dayz mod (overwatch) server.

I have been looking around on the internet and there was a lot of talk about people needing to tweak their my.ini in their mysql folder.
I have no knowledge of what to change. I copied someone's off the internet and it seems to do ok but Im wondering if someone who knows more could help me figure out the best possible values to use. Here is a copy of my.ini

Code: Select all

# Example MySQL config file for small systems.
#
# This is for a system with little memory (<= 64M) where MySQL is only used
# from time to time and it's important that the mysqld daemon
# doesn't use much resources.
#
# MySQL programs look for option files in a set of
# locations which depend on the deployment platform.
# You can copy this option file to one of those
# locations. For information about these locations, see:
# http://dev.mysql.com/doc/mysql/en/option-files.html
#
# In this file, you can use all long options that a program supports.
# If you want to know which options a program supports, run the program
# with the "--help" option.

# The following options will be passed to all MySQL clients
[client]
#password	= password
port		= 3306
socket		= /tmp/mysql.sock

# Here follows entries for some specific programs

# The MySQL server
[mysqld]
event_scheduler=ON
port		= 3306
socket		= /tmp/mysql.sock
skip-external-locking
key_buffer_size = 1000MB
max_allowed_packet = 256M
table_open_cache = 12
sort_buffer_size = 512K
read_buffer_size = 256K
read_rnd_buffer_size = 512K
net_buffer_length = 2K
thread_stack = 256K

# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (using the "enable-named-pipe" option) will render mysqld useless!
# 
#skip-networking
server-id	= 1

# Uncomment the following if you want to log updates
#log-bin=mysql-bin

# binary logging format - mixed recommended
#binlog_format=mixed

# Causes updates to non-transactional engines using statement format to be
# written directly to binary log. Before using this option make sure that
# there are no dependencies between transactional and non-transactional
# tables such as in the statement INSERT INTO t_myisam SELECT * FROM
# t_innodb; otherwise, slaves may diverge from the master.
#binlog_direct_non_transactional_updates=TRUE

# Uncomment the following if you are using InnoDB tables
innodb_data_home_dir = ../data/
innodb_data_file_path = ibdata1:10M:autoextend
innodb_log_group_home_dir = ../data/
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
innodb_buffer_pool_size = 1G
innodb_additional_mem_pool_size = 2M
# Set .._log_file_size to 25 % of buffer pool size
innodb_log_file_size = 250MB
innodb_log_buffer_size = 20M
innodb_flush_log_at_trx_commit = 2
innodb_lock_wait_timeout = 50

[mysqldump]
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[myisamchk]
key_buffer_size = 20M
sort_buffer_size = 20M

[mysqlhotcopy]
interactive-timeout
Thanks for any help
User avatar
Markie
A regular
A regular
Posts: 56
Joined: Mon Oct 01, 2012 11:55 am
Location: AS14586

Re: Need help tweaking my.ini

Post by Markie »

I think your best bet would be using the default settings first, then actively monitoring your system resources to see if any "tweaks" are needed. I would also recommend looking into the performance_schema storage engine.
Post Reply