I had couple ideas, want to see how you would design it.
OS: Ubuntu 12.04
Should support players: 2000
default engine: innoDB
RAM: 32 GB
cpu: 2xl5520
hdd: 250GB SAS
mysql: 5.5
default configs:
#
# The MySQL database server configuration file.
#
# You can copy this to one of:
# - "/etc/mysql/my.cnf" to set global options,
# - "~/.my.cnf" to set user-specific options.
#
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html
# This will be passed to all mysql clients
# It has been reported that passwords should be enclosed with ticks/quotes
# escpecially if they contain "#" chars...
# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
[client]
port = 3306
socket = /var/run/mysqld/mysqld.sock
# Here is entries for some specific programs
# The following values assume you have at least 32M ram
# This was formally known as [safe_mysqld]. Both versions are currently parsed.
[mysqld_safe]
socket = /var/run/mysqld/mysqld.sock
nice = 0
[mysqld]
#
# * Basic Settings
#
user = mysql
pid-file = /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock
port = 3306
basedir = /usr
datadir = /var/lib/mysql
tmpdir = /tmp
lc-messages-dir = /usr/share/mysql
skip-external-locking
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
bind-address = 127.0.0.1
#
# * Fine Tuning
#
key_buffer = 16M
max_allowed_packet = 16M
thread_stack = 192K
thread_cache_size = 8
# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched
myisam-recover = BACKUP
#max_connections = 100
#table_cache = 64
#thread_concurrency = 10
#
# * Query Cache Configuration
#
query_cache_limit = 1M
query_cache_size = 16M
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
# As of 5.1 you can enable the log at runtime!
#general_log_file = /var/log/mysql/mysql.log
#general_log = 1
#
# Error log - should be very few entries.
#
log_error = /var/log/mysql/error.log
#
# Here you can see queries with especially long duration
#log_slow_queries = /var/log/mysql/mysql-slow.log
#long_query_time = 2
#log-queries-not-using-indexes
#
# The following can be used as easy to replay backup logs or for replication.
# note: if you are setting up a replication slave, see README.Debian about
# other settings you may need to change.
#server-id = 1
#log_bin = /var/log/mysql/mysql-bin.log
expire_logs_days = 10
max_binlog_size = 100M
#binlog_do_db = include_database_name
#binlog_ignore_db = include_database_name
#
# * InnoDB
#
# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
# Read the manual for more InnoDB related options. There are many!
#
# * Security Features
#
# Read the manual, too, if you want chroot!
# chroot = /var/lib/mysql/
#
# For generating SSL certificates I recommend the OpenSSL GUI "tinyca".
#
# ssl-ca=/etc/mysql/cacert.pem
# ssl-cert=/etc/mysql/server-cert.pem
# ssl-key=/etc/mysql/server-key.pem
[mysqldump]
quick
quote-names
max_allowed_packet = 16M
[mysql]
#no-auto-rehash # faster start of mysql but no tab completition
[isamchk]
key_buffer = 16M
#
# * IMPORTANT: Additional settings that can override those from this file!
# The files must end with '.cnf', otherwise they'll be ignored.
#
!includedir /etc/mysql/conf.d/
Alright, since we’re already disturbing the dead, let me toss my shovel in too. Thanks for the update, this place hasn’t seen activity since Maxtor discovered extracurricular festivals, so any sign of life is basically breaking news at this point.
Arena, x200, 1+1 and now “final stages”? sounds like someone’s actually pushing this thing forward instead of just daydreaming on Discord. Good. Maybe some oxygen will flow back into this fossil of a forum.
As for staff recruitment… yeah, filtering out the “english no good but i can be gm pls sir” crowd is probably the smartest move I’ve seen here in years. Might actually keep the circus level to a minimum.
Post the site when it’s ready. Some of us are still lurking like cursed background processes you can’t kill even with kill -9.
And don’t worry about the whole “messenger” thing, nobody here cares enough to start drama. You could post patch notes written in crayon and half the userbase still wouldn’t log in (only the true @Kara can do that).
Anyway, keep the updates coming. If this project actually launches, it might be the first resurrection this graveyard has ever witnessed.
Selling interface source for newest client update rose vain p520 + wolf p509 (LAST UPDATE)
SYSTEM SERVER TEST
600$ (P520)
400$ (P509)
includes:
- NWindow
- L2 Editor
- DAT Editor
- Client+System clean
- Interface sources
- XDat Editor
ALL FEATURES ARE ONLY AVAILABLE IN THE P520 INTERFACE SOURCE
The P509 interface is retail.
ALL FEATURES ON P520
AUTOHUNT IMPROVED
GUARANTEED SYSTEM
AUTO-COMPOUND
MASS ENCHANT IMPROVED
ALL AVAILABLE SKILL LEARN
AUTO RANDOM CRAFT
SHORTCUT IMPROVED
Question
scr3ative
I had couple ideas, want to see how you would design it.
OS: Ubuntu 12.04
Should support players: 2000
default engine: innoDB
RAM: 32 GB
cpu: 2xl5520
hdd: 250GB SAS
mysql: 5.5
default configs:
Thanks!
8 answers to this question
Recommended Posts