database.sarang.net
UserID
Passwd
Database
DBMS
ㆍMySQL
PostgreSQL
Firebird
Oracle
Informix
Sybase
MS-SQL
DB2
Cache
CUBRID
LDAP
ALTIBASE
Tibero
DB 문서들
스터디
Community
공지사항
자유게시판
구인|구직
DSN 갤러리
도움주신분들
Admin
운영게시판
최근게시물
MySQL Q&A 29516 게시물 읽기
No. 29516
mysql 부하문제
작성자
byeong
작성일
2010-01-22 11:37
조회수
9,297

소통량 Tip ø per hour
받음 11 GB 102 MB
보냄 68 GB 624 MB
전체 사용량 79 GB 726 MB
연결 수 ø per hour %
max. concurrent connections 57 --- ---
실패한 시도 2,191 19.63 0.02%
Aborted 588 5.27 0.01%
전체 사용량 11 M 96.27 k 100.00%


SQL 질의 통계: 이 서버에 77,801,942 번의 질의가 보내졌습니다.

전체 사용량 ø per hour ø per minute ø per second
78 M 697.22 k 11.62 k 193.67

질의 종류 ø per hour %
admin commands 30 0.27 0.00%
alter db 0 0.00 0.00%
alter table 15 0.13 0.00%
analyze 0 0.00 0.00%
backup table 0 0.00 0.00%
begin 0 0.00 0.00%
change db 142 k 1,271.60 0.21%
change master 0 0.00 0.00%
check 0 0.00 0.00%
checksum 0 0.00 0.00%
commit 0 0.00 0.00%
create db 0 0.00 0.00%
create function 0 0.00 0.00%
create index 0 0.00 0.00%
create table 14 0.13 0.00%
delete 145 1.30 0.00%
delete multi 0 0.00 0.00%
do 0 0.00 0.00%
drop db 0 0.00 0.00%
drop function 0 0.00 0.00%
drop index 0 0.00 0.00%
drop table 2 0.02 0.00%
drop user 0 0.00 0.00%
flush 0 0.00 0.00%
grant 0 0.00 0.00%
ha close 0 0.00 0.00%
ha open 0 0.00 0.00%
ha read 0 0.00 0.00%
help 0 0.00 0.00%
insert 198 k 1,771.81 0.29%
insert select 9 0.08 0.00%
kill 1,747 15.66 0.00%
load 0 0.00 0.00%
load master data 0 0.00 0.00%
load master table 0 0.00 0.00%
lock tables 0 0.00 0.00%
optimize 1 8.96 m 0.00%
preload keys 0 0.00 0.00%
purge 0 0.00 0.00%
purge before date 0 0.00 0.00%
rename table 0 0.00 0.00%
repair 0 0.00 0.00%
replace 0 0.00 0.00%
replace select 0 0.00 0.00%
reset 0 0.00 0.00%
restore table 0 0.00 0.00%
revoke 0 0.00 0.00%
revoke all 0 0.00 0.00%
rollback 0 0.00 0.00%
질의 종류 ø per hour %
savepoint 0 0.00 0.00%
select 1,543 k 13.83 k 2.30%
set option 43 M 381.33 k 63.45%
show binlog events 4 0.04 0.00%
show binlogs 287 2.57 0.00%
show charsets 4,124 36.96 0.01%
show collations 11 M 95.35 k 15.87%
show column types 0 0.00 0.00%
show create db 0 0.00 0.00%
show create table 1,088 9.75 0.00%
show databases 4,127 36.98 0.01%
show errors 0 0.00 0.00%
show fields 3,408 30.54 0.01%
show grants 1,895 16.98 0.00%
show innodb status 0 0.00 0.00%
show keys 1,483 13.29 0.00%
show logs 0 0.00 0.00%
show master status 0 0.00 0.00%
show ndb status 0 0.00 0.00%
show new master 0 0.00 0.00%
show open tables 2 0.02 0.00%
show privileges 0 0.00 0.00%
show processlist 51 0.46 0.00%
show slave hosts 0 0.00 0.00%
show slave status 0 0.00 0.00%
show status 34 0.30 0.00%
show storage engines 24 0.22 0.00%
show tables 9,968 89.33 0.01%
show triggers 0 0.00 0.00%
show variables 11 M 95.39 k 15.87%
show warnings 0 0.00 0.00%
slave start 0 0.00 0.00%
slave stop 0 0.00 0.00%
stmt close 0 0.00 0.00%
stmt execute 4,143 37.13 0.01%
stmt fetch 0 0.00 0.00%
stmt prepare 4,143 37.13 0.01%
stmt reset 0 0.00 0.00%
stmt send long data 0 0.00 0.00%
truncate 11 0.10 0.00%
unlock tables 0 0.00 0.00%
update 373 k 3,342.01 0.56%
update multi 12 0.11 0.00%
xa commit 0 0.00 0.00%
xa end 0 0.00 0.00%
xa prepare 0 0.00 0.00%
xa recover 0 0.00 0.00%
xa rollback 0 0.00 0.00%
xa start 0 0.00 0.00%
처음
변수 Description
Flush_commands 1 The number of executed FLUSH statements.
Last_query_cost 0 The total cost of the last compiled query as computed by the query optimizer. Useful for comparing the cost of different query plans for the same query. The default value of 0 means that no query has been compiled yet.
Slow_queries 32 The number of queries that have taken more than long_query_time seconds. MySQL - 도움말
처음 InnoDB
변수 Description
환경설정값 InnoDB 상태 MySQL - 도움말
Innodb_buffer_pool_pages_data 20 The number of pages containing data (dirty or clean).
Innodb_buffer_pool_pages_dirty 0 The number of pages currently dirty.
Innodb_buffer_pool_pages_flushed 0 The number of buffer pool pages that have been requested to be flushed.
Innodb_buffer_pool_pages_free 492 The number of free pages.
Innodb_buffer_pool_pages_latched 0 The number of latched pages in InnoDB buffer pool. These are pages currently being read or written or that can't be flushed or removed for some other reason.
Innodb_buffer_pool_pages_misc 0 The number of pages busy because they have been allocated for administrative overhead such as row locks or the adaptive hash index. This value can also be calculated as Innodb_buffer_pool_pages_total - Innodb_buffer_pool_pages_free - Innodb_buffer_pool_pages_data.
Innodb_buffer_pool_pages_total 512 Total size of buffer pool, in pages.
Innodb_buffer_pool_read_ahead_rnd 1 The number of "random" read-aheads InnoDB initiated. This happens when a query is to scan a large portion of a table but in random order.
Innodb_buffer_pool_read_ahead_seq 0 The number of sequential read-aheads InnoDB initiated. This happens when InnoDB does a sequential full table scan.
Innodb_buffer_pool_read_requests 202 The number of logical read requests InnoDB has done.
Innodb_buffer_pool_reads 13 The number of logical reads that InnoDB could not satisfy from buffer pool and had to do a single-page read.
Innodb_buffer_pool_wait_free 0 Normally, writes to the InnoDB buffer pool happen in the background. However, if it's necessary to read or create a page and no clean pages are available, it's necessary to wait for pages to be flushed first. This counter counts instances of these waits. If the buffer pool size was set properly, this value should be small.
Innodb_buffer_pool_write_requests 0 The number writes done to the InnoDB buffer pool.
Innodb_data_fsyncs 3 The number of fsync() operations so far.
Innodb_data_pending_fsyncs 0 The current number of pending fsync() operations.
Innodb_data_pending_reads 0 The current number of pending reads.
Innodb_data_pending_writes 0 The current number of pending writes.
Innodb_data_read 2,773 k The amount of data read so far, in bytes.
Innodb_data_reads 42 The total number of data reads.
Innodb_data_writes 3 The total number of data writes.
Innodb_data_written 1,536 The amount of data written so far, in bytes.
Innodb_dblwr_pages_written 0 The number of doublewrite writes that have been performed and the number of pages that have been written for this purpose.
Innodb_dblwr_writes 0 The number of doublewrite writes that have been performed and the number of pages that have been written for this purpose.
Innodb_log_waits 0 The number of waits we had because log buffer was too small and we had to wait for it to be flushed before continuing.
Innodb_log_write_requests 0 The number of log write requests.
Innodb_log_writes 1 The number of physical writes to the log file.
Innodb_os_log_fsyncs 3 The number of fsyncs writes done to the log file.
Innodb_os_log_pending_fsyncs 0 The number of pending log file fsyncs.
Innodb_os_log_pending_writes 0 Pending log file writes.
Innodb_os_log_written 512 The number of bytes written to the log file.
Innodb_page_size 16 k The compiled-in InnoDB page size (default 16KB). Many values are counted in pages; the page size allows them to be easily converted to bytes.
Innodb_pages_created 0 The number of pages created.
Innodb_pages_read 20 The number of pages read.
Innodb_pages_written 0 The number of pages written.
Innodb_row_lock_current_waits 0 The number of row locks currently being waited for.
Innodb_row_lock_time 0 The total time spent in acquiring row locks, in milliseconds.
Innodb_row_lock_time_avg 0 The average time to acquire a row lock, in milliseconds.
Innodb_row_lock_time_max 0 The maximum time to acquire a row lock, in milliseconds.
Innodb_row_lock_waits 0 The number of times a row lock had to be waited for.
Innodb_rows_deleted 0 The number of rows deleted from InnoDB tables.
Innodb_rows_inserted 0 The number of rows inserted in InnoDB tables.
Innodb_rows_read 0 The number of rows read from InnoDB tables.
Innodb_rows_updated 0 The number of rows updated in InnoDB tables.
처음 Handler
변수 Description
Handler_commit 0 The number of internal COMMIT statements.
Handler_delete 137 The number of times a row was deleted from a table.
Handler_discover 0 The MySQL server can ask the NDB Cluster storage engine if it knows about a table with a given name. This is called discovery. Handler_discover indicates the number of time tables have been discovered.
Handler_prepare 0  
Handler_read_first 2,519 The number of times the first entry was read from an index. If this is high, it suggests that the server is doing a lot of full index scans; for example, SELECT col1 FROM foo, assuming that col1 is indexed.
Handler_read_key 9,870 k The number of requests to read a row based on a key. If this is high, it is a good indication that your queries and tables are properly indexed.
Handler_read_next 20 M The number of requests to read the next row in key order. This is incremented if you are querying an index column with a range constraint or if you are doing an index scan.
Handler_read_prev 8,427 The number of requests to read the previous row in key order. This read method is mainly used to optimize ORDER BY ... DESC.
Handler_read_rnd 1,094 k The number of requests to read a row based on a fixed position. This is high if you are doing a lot of queries that require sorting of the result. You probably have a lot of queries that require MySQL to scan whole tables or you have joins that don't use keys properly.
Handler_read_rnd_next 79 G The number of requests to read the next row in the data file. This is high if you are doing a lot of table scans. Generally this suggests that your tables are not properly indexed or that your queries are not written to take advantage of the indexes you have.
Handler_rollback 0 The number of internal ROLLBACK statements.
Handler_savepoint 0  
Handler_savepoint_rollback 0  
Handler_update 330 k The number of requests to update a row in a table.
Handler_write 3,685 M The number of requests to insert a row in a table.
처음 Query cache
변수 Description
Flush query cache MySQL - 도움말
Qcache_free_blocks 3,915 The number of free memory blocks in query cache.
Qcache_free_memory 11 M The amount of free memory for query cache.
Qcache_hits 922 k The number of cache hits.
Qcache_inserts 1,521 k The number of queries added to the cache.
Qcache_lowmem_prunes 143 k The number of queries that have been removed from the cache to free up memory for caching new queries. This information can help you tune the query cache size. The query cache uses a least recently used (LRU) strategy to decide which queries to remove from the cache.
Qcache_not_cached 21 M The number of non-cached queries (not cachable, or not cached due to the query_cache_type setting).
Qcache_queries_in_cache 7,980 The number of queries registered in the cache.
Qcache_total_blocks 20 k The total number of blocks in the query cache.
처음 Threads
변수 Description
MySQL 프로세스 보기 MySQL - 도움말
Slow_launch_threads 0 The number of threads that have taken more than slow_launch_time seconds to create.
Threads_cached 6 The number of threads in the thread cache. The cache hit rate can be calculated as Threads_created/Connections. If this value is red you should raise your thread_cache_size.
Threads_connected 4 The number of currently open connections.
Threads_created 658 The number of threads created to handle connections. If Threads_created is big, you may want to increase the thread_cache_size value. (Normally this doesn't give a notable performance improvement if you have a good thread implementation.)
Threads_running 2 The number of threads that are not sleeping.
Threads_cache_hitrate_% 99.99 %  
처음 Binary log
변수 Description
MySQL - 도움말
Binlog_cache_disk_use 0 The number of transactions that used the temporary binary log cache but that exceeded the value of binlog_cache_size and used a temporary file to store statements from the transaction.
Binlog_cache_use 0 The number of transactions that used the temporary binary log cache.
처음 Temporary data
변수 Description
Created_tmp_disk_tables 3,476 The number of temporary tables on disk created automatically by the server while executing statements. If Created_tmp_disk_tables is big, you may want to increase the tmp_table_size value to cause temporary tables to be memory-based instead of disk-based.
Created_tmp_files 14 k How many temporary files mysqld has created.
Created_tmp_tables 21 M The number of in-memory temporary tables created automatically by the server while executing statements.
처음 Delayed inserts
변수 Description
Delayed_errors 0 The number of rows written with INSERT DELAYED for which some error occurred (probably duplicate key).
Delayed_insert_threads 0 The number of INSERT DELAYED handler threads in use. Every different table on which one uses INSERT DELAYED gets its own thread.
Delayed_writes 0 The number of INSERT DELAYED rows written.
Not_flushed_delayed_rows 0 The number of rows waiting to be written in INSERT DELAY queues.
처음 Key cache
변수 Description
MySQL - 도움말
Key_blocks_not_flushed 0 The number of key blocks in the key cache that have changed but haven't yet been flushed to disk. It used to be known as Not_flushed_key_blocks.
Key_blocks_unused 268 k The number of unused blocks in the key cache. You can use this value to determine how much of the key cache is in use.
Key_blocks_used 56 k The number of used blocks in the key cache. This value is a high-water mark that indicates the maximum number of blocks that have ever been in use at one time.
Key_read_requests 40 M The number of requests to read a key block from the cache.
Key_reads 58 k The number of physical reads of a key block from disk. If Key_reads is big, then your key_buffer_size value is probably too small. The cache miss rate can be calculated as Key_reads/Key_read_requests.
Key_write_requests 907 k The number of requests to write a key block to the cache.
Key_writes 264 k The number of physical writes of a key block to disk.
Key_buffer_fraction_% 31.90 %  
Key_write_ratio_% 29.06 %  
Key_read_ratio_% 0.15 %  
처음 Joins
변수 Description
Select_full_join 146 The number of joins that do not use indexes. If this value is not 0, you should carefully check the indexes of your tables.
Select_full_range_join 0 The number of joins that used a range search on a reference table.
Select_range 1,549 The number of joins that used ranges on the first table. (It's normally not critical even if this is big.)
Select_range_check 0 The number of joins without keys that check for key usage after each row. (If this is not 0, you should carefully check the indexes of your tables.)
Select_scan 22 M The number of joins that did a full scan of the first table.
처음 Replication
변수 Description
Show slave hosts Show slave status MySQL - 도움말
Rpl_status NULL The status of failsafe replication (not yet implemented).
Slave_open_temp_tables 0 The number of temporary tables currently open by the slave SQL thread.
Slave_retried_transactions 0 Total (since startup) number of times the replication slave SQL thread has retried transactions.
Slave_running OFF This is ON if this server is a slave that is connected to a master.
처음 Sorting
변수 Description
Sort_merge_passes 11 k The number of merge passes the sort algorithm has had to do. If this value is large, you should consider increasing the value of the sort_buffer_size system variable.
Sort_range 16 The number of sorts that were done with ranges.
Sort_rows 347 M The number of sorted rows.
Sort_scan 43 k The number of sorts that were done by scanning the table.
처음 테이블 수
변수 Description
Flush (close) all tables Show open tables
Open_tables 662 The number of tables that are open.
Opened_tables 749 The number of tables that have been opened. If opened tables is big, your table cache value is probably too small.
Table_locks_immediate 2,145 k The number of times that a table lock was acquired immediately.
Table_locks_waited 262 The number of times that a table lock could not be acquired immediately and a wait was needed. If this is high, and you have performance problems, you should first optimize your queries, and then either split your table or tables or use replication.
처음 Transaction coordinator
변수 Description
Tc_log_max_pages_used 0  
Tc_log_page_size 0  
Tc_log_page_waits 0  
처음
변수 Description
Compression OFF  
Open_files 1,191 The number of files that are open.
Open_streams 0 The number of streams that are open (used mainly for logging).

보시는 것처럼 소통량이 엄청납니다.

접속자도 없고 쿼리도 보내지 않고 있는데 저렇네요

 

해결법을 검색해도 잘 모르겠네요... 아시는분은 좀 알려주세요

이 글에 대한 댓글이 총 2건 있습니다.

 

 

table_cache 를 한번 올려보세요~

민족님이 2010-01-26 10:21에 작성한 댓글입니다. Edit

auto increment increment 1
auto increment offset 1
automatic sp privileges ON
back log 50
basedir /usr/local/mysql/
binlog cache size 32,768
bulk insert buffer size 8,388,608
character set client utf8
(Global value) euckr
character set connection utf8
(Global value) euckr
character set database euckr
character set filesystem binary
character set results utf8
(Global value) euckr
character set server euckr
character set system utf8
character sets dir /usr/local/mysql/share/mysql/charsets/
collation connection utf8_unicode_ci
(Global value) euckr_korean_ci
collation database euckr_korean_ci
collation server euckr_korean_ci
completion type 0
concurrent insert 1
connect timeout 5
datadir /home/mysql_data/
date format %Y-%m-%d
datetime format %Y-%m-%d %H:%i:%s
default week format 0
delay key write ON
delayed insert limit 100
delayed insert timeout 300
delayed queue size 1,000
div precision increment 4
engine condition pushdown OFF
expire logs days 0
flush OFF
flush time 0
ft boolean syntax + -><()~*:""&|
ft max word len 84
ft min word len 4
ft query expansion limit 20
ft stopword file (built-in)
group concat max len 1,024
have archive NO
have bdb NO
have blackhole engine NO
have compress YES
have crypt YES
have csv NO
have dynamic loading YES
have example engine NO
have federated engine NO
have geometry YES
have innodb YES
have isam NO
have merge engine YES
have ndbcluster NO
have openssl NO
have query cache YES
have raid NO
have rtree keys YES
have symlink YES
init connect  
init file  
init slave  
innodb additional mem pool size 1,048,576
innodb autoextend increment 8
innodb buffer pool awe mem mb 0
innodb buffer pool size 8,388,608
innodb checksums ON
innodb commit concurrency 0
innodb concurrency tickets 500
innodb data file path ibdata1:10M:autoextend
innodb data home dir  
innodb doublewrite ON
innodb fast shutdown 1
innodb file io threads 4
innodb file per table OFF
innodb flush log at trx commit 1
innodb flush method  
innodb force recovery 0
innodb lock wait timeout 50
innodb locks unsafe for binlog OFF
innodb log arch dir  
innodb log archive OFF
innodb log buffer size 1,048,576
innodb log file size 5,242,880
innodb log files in group 2
innodb log group home dir ./
innodb max dirty pages pct 90
innodb max purge lag 0
innodb mirrored log groups 1
innodb open files 300
innodb support xa ON
innodb sync spin loops 20
innodb table locks ON
innodb thread concurrency 8
innodb thread sleep delay 10,000
interactive timeout 1,800
join buffer size 2,093,056
key buffer size 402,653,184
key cache age threshold 300
key cache block size 1,024
key cache division limit 100
language /usr/local/mysql/share/mysql/english/
large files support ON
large page size 0
large pages OFF
lc time names en_US
license GPL
local infile ON
locked in memory OFF
log OFF
log bin ON
log bin trust function creators OFF
log error  
log queries not using indexes OFF
log slave updates OFF
log slow queries OFF
log warnings 1
long query time 10
low priority updates OFF
lower case file system OFF
lower case table names 0
max allowed packet 4,193,280
max binlog cache size 18446744073709551615
max binlog size 1,073,741,824
max connect errors 30
max connections 1,000
max delayed threads 20
max error count 64
max heap table size 16,777,216
max insert delayed threads 20
max join size 18446744073709551615
max length for sort data 1,024
max prepared stmt count 16,382
max relay log size 0
max seeks for key 18446744073709551615
max sort length 1,024
max sp recursion depth 0
max tmp tables 32
max user connections 0
max write lock count 18446744073709551615
multi range count 256
myisam data pointer size 6
myisam max sort file size 9223372036854775807
myisam recover options OFF
myisam repair threads 1
myisam sort buffer size 67,108,864
myisam stats method nulls_unequal
net buffer length 16,384
net read timeout 30
net retry count 10
net write timeout 60
new OFF
old passwords OFF
open files limit 17,394
optimizer prune level 1
optimizer search depth 62
pid file /home/mysql_data/localhost.pid
port 3,306
preload buffer size 32,768
prepared stmt count 0
protocol version 10
query alloc block size 8,192
query cache limit 1,048,576
query cache min res unit 4,096
query cache size 33,554,432
query cache type ON
query cache wlock invalidate OFF
query prealloc size 8,192
range alloc block size 2,048
read buffer size 131,072
read only OFF
read rnd buffer size 8,384,512
relay log purge ON
relay log space limit 0
rpl recovery rank 0
secure auth OFF
server id 1
skip external locking ON
skip networking OFF
skip show database OFF
slave compressed protocol OFF
slave load tmpdir /tmp/
slave net timeout 3,600
slave skip errors OFF
slave transaction retries 10
slow launch time 2
socket /tmp/mysql.sock
sort buffer size 2,097,144
sql big selects ON
sql mode  
sql notes ON
sql warnings OFF
ssl ca  
ssl capath  
ssl cert  
ssl cipher  
ssl key  
storage engine MyISAM
sync binlog 0
sync frm ON
system time zone KST
table cache 8,192
table lock wait timeout 50
table type MyISAM
thread cache size 8
thread stack 262,144
time format %H:%i:%s
time zone SYSTEM
timed mutexes OFF
tmp table size 33,554,432
tmpdir /tmp/
transaction alloc block size 8,192
transaction prealloc size 4,096
tx isolation REPEATABLE-READ
updatable views with limit YES
version 5.0.27-log
version comment Source distribution
version compile machine x86_64
version compile os unknown-linux-gnu
wait timeout

 

환경설정값입니다. table_cashe 가 8162로 되어있는데 어느정도 더 올려야할까요???

byeong님이 2010-01-27 09:21에 작성한 댓글입니다. Edit
[Top]
No.
제목
작성자
작성일
조회
29519[ㄱㄱ 급--mysql.tar 복구 방법있나요???] [3]
장상민
2010-01-26
6240
29518mysql err파일좀 봐주세요.ㅠ [1]
방방방
2010-01-25
6944
29517[질문]필드 문자열처리입니다.
홍창용
2010-01-24
6176
29516mysql 부하문제 [2]
byeong
2010-01-22
9297
29515MySQL에서 C API 사용 ^^ [1]
맥초보
2010-01-21
6304
29513like 와 INSTR 어떻게 속도 면에서 좋아요? [1]
홍길동
2010-01-21
9412
29511서브쿼리 속도 [1]
궁금이
2010-01-19
6940
Valid XHTML 1.0!
All about the DATABASE... Copyleft 1999-2024 DSN, All rights reserved.
작업시간: 0.018초, 이곳 서비스는
	PostgreSQL v16.2로 자료를 관리합니다