Co należy zmienić?

[jabuszko]

Witam. Od tygodnia posiadam dedyka gdzie przeniosłem swoja stronke. Strona w ciagu 3 dni wygeneroala 11 000 000 zapytan do bazy danych.

Oto wyniki z Tuning Primer

Uptime = 4 days 6 hrs 30 min 40 sec

Avg. qps = 30

Total Questions = 11295240

Threads Connected = 1

Server has been running for over 48hrs.

It should be safe to follow these recommendations

To find out more information on how each of these

runtime variables effects performance visit:

https://dev.mysql.com...-variables.html

Visit https://www.mysql.com...e/advisors.html

for info about MySQL's Enterprise Monitoring and Advisory Service

SLOW QUERIES

The slow query log is NOT enabled.

Current long_query_time = 10 sec.

You have 0 out of 11295261 that take longer than 10 sec. to complete

Your long_query_time seems to be fine

BINARY UPDATE LOG

The binary update log is NOT enabled.

You will not be able to do point in time recovery

See https://dev.mysql.com...e-recovery.html

WORKER THREADS

Current thread_cache_size = 8

Current threads_cached = 7

Current threads_per_sec = 0

Historic threads_per_sec = 0

Your thread_cache_size is fine

MAX CONNECTIONS

Current max_connections = 100

Current threads_connected = 1

Historic max_used_connections = 101

The number of used connections is 101% of the configured maximum.

You should raise max_connections

INNODB STATUS

Current InnoDB index space = 0 bytes

Current InnoDB data space = 0 bytes

Current InnoDB buffer pool free = 65 %

Current innodb_buffer_pool_size = 8 M

Depending on how much space your innodb indexes take up it may be safe

to increase this value to up to 2 / 3 of total system memory

MEMORY USAGE

Max Memory Ever Allocated : 307 M

Configured Max Per-thread Buffers : 262 M

Configured Max Global Buffers : 42 M

Configured Max Memory Limit : 304 M

Physical Memory : 3.83 G

Max memory limit seem to be within acceptable norms

KEY BUFFER

Current MyISAM index space = 2 M

Current key_buffer_size = 16 M

Key cache miss rate is 1 : 2441

Key buffer free ratio = 81 %

Your key_buffer_size seems to be fine

QUERY CACHE

Query cache is enabled

Current query_cache_size = 16 M

Current query_cache_used = 5 M

Current query_cache_limit = 1 M

Current Query cache Memory fill ratio = 32.22 %

Current query_cache_min_res_unit = 4 K

MySQL won't cache query results that are larger than query_cache_limit in size

SORT OPERATIONS

Current sort_buffer_size = 2 M

Current read_rnd_buffer_size = 256 K

Sort buffer seems to be fine

JOINS

Current join_buffer_size = 132.00 K

You have had 1 queries where a join could not use an index properly

You should enable "log-queries-not-using-indexes"

Then look for non indexed joins in the slow query log.

If you are unable to optimize your queries you may want to increase your

join_buffer_size to accommodate larger joins in one pass.

Note! This script will still suggest raising the join_buffer_size when

ANY joins not using indexes are found.

OPEN FILES LIMIT

Current open_files_limit = 1024 files

The open_files_limit should typically be set to at least 2x-3x

that of table_cache if you have heavy MyISAM usage.

Your open_files_limit value seems to be fine

TABLE CACHE

Current table_cache value = 64 tables

You have a total of 73 tables

You have 64 open tables.

Current table_cache hit rate is 2%

, while 100% of your table cache is in use

You should probably increase your table_cache

TEMP TABLES

Current max_heap_table_size = 16 M

Current tmp_table_size = 32 M

Of 4077 temp tables, 11% were created on disk

Effective in-memory tmp_table_size is limited to max_heap_table_size.

Created disk tmp tables ratio seems fine

TABLE SCANS

Current read_buffer_size = 128 K

Current table scan ratio = 307 : 1

read_buffer_size seems to be fine

TABLE LOCKING

Current Lock Wait ratio = 1 : 285

You may benefit from selective use of InnoDB.

If you have long running SELECT's against MyISAM tables and perform

frequent updates consider setting 'low_priority_updates=1'

If you have a high concurrency of inserts on Dynamic row-length tables

consider setting 'concurrent_insert=2'.

Prosił bym o poradę co zmienić bo w momencie dużego "ataku" użytkowników na stronę dość długo się ona ładuje.

Intel® Core™2 Quad CPU Q8300 @ 2.50GHz, 4 cores

4 GB Ramu

System Debian 5

W czasie tego obciążenia Webmin pokazuje użycie procka na poziomie 1,00 % ;O

[Mion]

Zastosować cachowanie elementów stron [lub samych zapytań] wykonujących kosztowne zapytania do bazy;

Zoptymalizować konfigurację samej bazy MySQL;

Można też zastosować mechanizm chroniący - blokujacy przed nieuzasadnianą ilością żądań z danego IP w jednostce czasu.

Tak na marginesie, to może masz błędy w skryptach i następuje zapętlanie i stąd taka liczba zapytań do bazy.

Z "fusów" nic więcej się powiedzieć na ten temat nie da...

[jabuszko]

odnośnie ilości zapytań to wątpie gdyż strona jest bardzo popularna i mamy bardzo dużo odwiedzin.

[Zielkq]

Jedno nie wyklucza drugiego... Duża ilość użytkowników + błąd w skrypcie może się równać jeszcze większej ilości zapytań...

[Mion]

Tak jak napisałem fusyyyyy .

Bez audytu oprogramowania nic się na da powiedzieć...