Медленные запросы MySQl

я не понял вопроса

лолз, первый п4 был с частотой 1,4ггц ласт 3,8 ггц , он спрашует какой там...

ааа... 2.5

Блин я в замешательстве, может дело все-таки в загруженной бд, а не в кривых запросах опенстатса

Смысла нет "замешиваться", на картинке представлен уже прокешированный запрос. Если запустить на П4 такую базу в продакшн хотя на бы 5 человек одновременной работы с сайтом, то он просто пукнет.

Вообще надо фиксить работу с ключами, менять класс БД, юзать PDO или mysqli, юзать подготовленные запросы (prepare) для разгона выборки.


---


По поводу страницы топа игроков:

Офф. ссылка: http://www.codelain.com/forum/index.php?topic=14297.msg125402#msg125402

нет.

Из меделенных запросов:

Код:

select name,server, (((((kills-deaths+assists*0.5+towerkills*0.5+raxkills*0.2+(courierkills+creepdenies)*0.1+neutralkills*0.03+creepkills*0.03) * .2)+(wins-losses)))*10) as totalscore from(select *, (kills/deaths) as killdeathratio, (totgames-wins) as losses from (select gp.name as name,ga.server as server,gp.gameid as gameid, gp.colour as colour, avg(dp.courierkills) as courierkills, sum(dp.raxkills) as raxkillstotal, sum(dp.towerkills) as towerkillstotal, sum(dp.assists) as assiststotal, sum(dp.courierkills) as courierkillstotal, sum(dp.creepdenies) as creepdeniestotal, sum(dp.creepkills) as creepkillstotal, sum(dp.neutralkills) as neutralkillstotal, sum(dp.deaths) as deathstotal, sum(dp.kills) as killstotal, avg(dp.raxkills) as raxkills,avg(dp.towerkills) as towerkills, avg(dp.assists) as assists, avg(dp.creepdenies) as creepdenies, avg(dp.creepkills) as creepkills,avg(dp.neutralkills) as neutralkills, avg(dp.deaths) as deaths, avg(dp.kills) as kills,count(*) as totgames, SUM(case when((dg.winner = 1 and dp.newcolour < 6) or (dg.winner = 2 and dp.newcolour > 6)) then 1 else 0 end) as wins from gameplayers as gp, dotagames as dg, games as ga,dotaplayers as dp where dg.winner <> 0 and dp.gameid = gp.gameid and dg.gameid = dp.gameid and dp.gameid = ga.id and gp.gameid = dg.gameid and gp.colour = dp.colour group by gp.name having totgames >= 5) as h) as i ORDER BY totalscore desc, name asc;
SET timestamp=1320410990;
# Query_time: 25.251032  Lock_time: 0.000239 Rows_sent: 17300  Rows_examined: 1885501
# User@Host: ghost[ghost] @ localhost []
# Time: 111104 15:49:50

Он в основном и гложет все. Я не знаю как у вас оно быстро работает.

Код:

SET query_cache_type = OFF; -- если query cache включен, выключаем его
FLUSH STATUS; -- скоро поймете :)
select name,server, (((((kills-deaths+assists*0.5+towerkills*0.5+raxkills*0.2+(courierkills+creepdenies)*0.1+neutralkills*0.03+creepkills*0.03) * .2)+(wins-losses)))*10) as totalscore from(select *, (kills/deaths) as killdeathratio, (totgames-wins) as losses from (select gp.name as name,ga.server as server,gp.gameid as gameid, gp.colour as colour, avg(dp.courierkills) as courierkills, sum(dp.raxkills) as raxkillstotal, sum(dp.towerkills) as towerkillstotal, sum(dp.assists) as assiststotal, sum(dp.courierkills) as courierkillstotal, sum(dp.creepdenies) as creepdeniestotal, sum(dp.creepkills) as creepkillstotal, sum(dp.neutralkills) as neutralkillstotal, sum(dp.deaths) as deathstotal, sum(dp.kills) as killstotal, avg(dp.raxkills) as raxkills,avg(dp.towerkills) as towerkills, avg(dp.assists) as assists, avg(dp.creepdenies) as creepdenies, avg(dp.creepkills) as creepkills,avg(dp.neutralkills) as neutralkills, avg(dp.deaths) as deaths, avg(dp.kills) as kills,count(*) as totgames, SUM(case when((dg.winner = 1 and dp.newcolour < 6) or (dg.winner = 2 and dp.newcolour > 6)) then 1 else 0 end) as wins from gameplayers as gp, dotagames as dg, games as ga,dotaplayers as dp where dg.winner <> 0 and dp.gameid = gp.gameid and dg.gameid = dp.gameid and dp.gameid = ga.id and gp.gameid = dg.gameid and gp.colour = dp.colour group by gp.name having totgames >= 5) as h) as i ORDER BY totalscore desc, name asc;
SHOW SESSION STATUS LIKE 'handler_%' -- магия ;)!

Почему не EXPLAIN если что:
http://habrahabr.ru/blogs/mysql/130905/

Получил:

Код:

Handler_commit	1
Handler_delete	0
Handler_discover	0
Handler_prepare	0
Handler_read_first	1
Handler_read_key	1140045
Handler_read_last	0
Handler_read_next	801515
Handler_read_prev	0
Handler_read_rnd	609524
Handler_read_rnd_next	191210
Handler_rollback	0
Handler_savepoint	0
Handler_savepoint_rollback	0
Handler_update	748266
Handler_write	701501

Я не понимаю почему оно у вас так быстро
my.cfg (у меня линупс, а не винда поэтому не my.ini)

Код:

# MySQL config file for medium systems.
#
# This is for a system with little memory (32M - 64M) where MySQL plays
# an important part, or systems up to 128M where MySQL is used together with
# other programs (such as a web server)
#
# 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	= your_password
port		= 3306
socket		= /var/run/mysqld/mysqld.sock

# Here follows entries for some specific programs

# The MySQL server
[mysqld]
max_connections = 1000
init_connect='SET collation_connection = utf8_general_ci'
init_connect='SET NAMES utf8'
character-set-server = 'utf8'
collation-server = 'utf8_general_ci'
#skip-character-set-client-handshake
port		= 3306
socket		= /var/run/mysqld/mysqld.sock
datadir		= /var/lib/mysql
skip-external-locking
#max_connections = 25000
query_cache_size = 186M
table_cache = 1520
tmp_table_size = 1024M
thread_cache_size = 38

myisam_max_sort_file_size = 100G
myisam_sort_buffer_size = 67M
key_buffer_size = 512M
read_buffer_size = 64K
read_rnd_buffer_size = 128M
sort_buffer_size = 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
# (via the "enable-named-pipe" option) will render mysqld useless!
# 
#skip-networking

# Replication Master Server (default)
# binary logging is required for replication
log-bin=mysql-bin

# binary logging format - mixed recommended
binlog_format=mixed

# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id	= 1

# Replication Slave (comment out master section to use this)
#
# To configure this host as a replication slave, you can choose between
# two methods :
#
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
#    the syntax is:
#
#    CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
#    MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
#
#    where you replace <host>, <user>, <password> by quoted strings and
#    <port> by the master's port number (3306 by default).
#
#    Example:
#
#    CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
#    MASTER_USER='joe', MASTER_PASSWORD='secret';
#
# OR
#
# 2) Set the variables below. However, in case you choose this method, then
#    start replication for the first time (even unsuccessfully, for example
#    if you mistyped the password in master-password and the slave fails to
#    connect), the slave will create a master.info file, and any later
#    change in this file to the variables' values below will be ignored and
#    overridden by the content of the master.info file, unless you shutdown
#    the slave server, delete master.info and restart the slaver server.
#    For that reason, you may want to leave the lines below untouched
#    (commented) and instead use CHANGE MASTER TO (see above)
#
# required unique id between 2 and 2^32 - 1
# (and different from the master)
# defaults to 2 if master-host is set
# but will not function as a slave if omitted
#server-id       = 2
#
# The replication master for this slave - required
#master-host     =   <hostname>
#
# The username the slave will use for authentication when connecting
# to the master - required
#master-user     =   <username>
#
# The password the slave will authenticate with when connecting to
# the master - required
#master-password =   <password>
#
# The port the master is listening on.
# optional - defaults to 3306
#master-port     =  <port>
#
# binary logging - not required for slaves, but recommended
#log-bin=mysql-bin

# Uncomment the following if you are using InnoDB tables
innodb_data_home_dir = /var/lib/mysql
innodb_data_file_path = ibdata1:10M:autoextend
innodb_log_group_home_dir = /var/lib/mysql
innodb_additional_mem_pool_size = 12M
innodb_flush_log_at_trx_commit = 1
innodb_log_buffer_size = 6M
innodb_buffer_pool_size = 563M
#innodb_log_file_size = 24M
innodb_thread_concurrency = 18

# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
#innodb_buffer_pool_size = 16M
#innodb_additional_mem_pool_size = 2M
# Set .._log_file_size to 25 % of buffer pool size
#innodb_log_file_size = 5M
#innodb_log_buffer_size = 8M
#innodb_flush_log_at_trx_commit = 1
#innodb_lock_wait_timeout = 50
# логгируем запросы длиннее 5 секунд
 long_query_time = 0.2
 # логгируем запросы, не использующие индексы
# log-queries-not-using-indexes
log-slow-queries= /var/log/mysql/slow.log
[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
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout

Я знаю как лучше, бы надо сделать, но все же у меня вопрос почему у других в разы быстрее, наврятли это из-за кеша в бд

GrayTroll, дело всё в том, что многие уже давно не используют стандартные запросы OS, да Лонг?

А поподробнее

запрос на подсчет очей, быстро работать не может, так как при этом выполняются довольно много операций, меняй запрос, юзай дота_ело или чтото типа дота_ело.

жал 1 раз, это форум