Czy coś jeszcze z tego wyciągnę?

[mrjozo 0]

Witam,

 

Mam serwerek:

Kimsufi 08 XXL Reloaded

Intel Core2Duo E7200 2x 2.53

ram:3 GB dysk: 500 GB IDE/SATA

luty transfer: Bandwidth (gb) 523.78

 

top - 12:54:16 up 19:56, 2 users, load average: 6.06, 4.48, 3.38
Tasks: 210 total, 3 running, 207 sleeping, 0 stopped, 0 zombie
Cpu(s): 24.0%us, 12.4%sy, 0.0%ni, 0.0%id, 61.2%wa, 0.0%hi, 2.5%si, 0.0%st
Mem: 3079540k total, 2608032k used, 471508k free, 114392k buffers
Swap: 522104k total,	34616k used, 487488k free, 1645820k cached

 

32337 apache	40 0 303m 37m 18m S 14 1.2 0:00.63 httpd
32332 apache	40 0 296m 28m 15m S 13 0.9 0:00.61 httpd
30227 apache	40 0 305m 53m 32m S 13 1.8 0:14.76 httpd
30228 apache	40 0 302m 50m 32m R	9 1.7 0:14.25 httpd
19842 nginx 	40 0 43412 39m 672 S	8 1.3 1:03.66 nginx
31312 mysql 	40 0 454m 91m 5360 S	4 3.0 0:23.15 mysqld
30215 apache	40 0 300m 45m 30m S	3 1.5 0:13.37 httpd
19843 nginx 	40 0 36600 32m 672 S	3 1.1 1:02.95 nginx
32313 apache	40 0 304m 32m 13m S	3 1.1 0:00.60 httpd
30191 apache	40 0 299m 45m 30m S	2 1.5 0:15.46 httpd
30195 apache	40 0 304m 52m 32m S	2 1.7 0:13.75 httpd
32306 apache	40 0 297m 22m 10m S	2 0.7 0:00.19 httpd
32325 apache	40 0 297m 28m 15m S	2 1.0 0:00.59 httpd

 

do lutego było jeszcze w miarę, w lutym wrzuciłem na serwer joomlę co spowodowało, że load jest niemiłosierny

na serwerze jest nginx jako proxy dla apache, mysql po lekkim tuningu, varnish, xache

z tego co widzę wa utrzymuje się na dużym poziomie, procesor jeszcze daje rade, avg load skacze pod 20:/

czy czas zmienic maszynke? czy takie wysokie wa moze wskazywac ze dysk pada?

[Gość N3T5kY]

1. Load w Linuxie (właśnie, nie podałeś systemu ), bez dostępu do serwera pozostaje tylko liczbą.

2. Podaj konfig apache

3. Konfig mysql

4. Nie wklejaj na wklej.org, tylko na forum przyda się pewnie komuś.

[mrjozo 0]

debian 4.0

 

mysql:

[mysqld]
#max_connections=500
long_query_time=1
log-slow-queries=/var/log/mysql/log-slow-queries.log
log-queries-not-using-indexes

local-infile=0
key_buffer = 200M 
max_allowed_packet = 32M
#thread_stack = 128K
thread_cache_size = 200 
max_connections = 200 
table_cache = 5K 
thread_concurrency = 8 
concurrent_insert = 2 
tmp_table_size = 200M #150M 
max_heap_table_size = 100M 
sort_buffer_size = 1M 
read_buffer_size = 1M 
join_buffer_size = 1M 
read_rnd_buffer_size = 1M 
open_files_limit = 8192
#connect_timeout = 120
wait_timeout = 60

#
# * Query Cache Configuration
#

query_cache_type = 1 
query_cache_limit = 4M 
query_cache_size = 100M 
query_cache_min_res_unit = 2K

# InnoDB
innodb_buffer_pool_size = 32M
innodb_thread_concurrency = 8 
innodb_flush_log_at_trx_commit = 0 
#innodb_log_file_size = 64M
innodb_log_buffer_size = 16M 
transaction-isolation = READ-COMMITTED 
innodb_flush_method = O_DIRECT

 

apache jest z da + zmiany w mpm:

#
# Server-Pool Management (MPM specific)
# 

#
# PidFile: The file in which the server should record its process
# identification number when it starts.
#
# Note that this is the default PidFile for most MPMs.
#
<IfModule !mpm_netware_module>
PidFile "/var/run/httpd.pid"
</IfModule>

#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
<IfModule !mpm_winnt_module>
<IfModule !mpm_netware_module>
LockFile /var/logs/accept.lock
</IfModule>
</IfModule>

#
# Only one of the below sections will be relevant on your
# installed httpd. Use "apachectl -l" to find out the
# active mpm.
#

# prefork MPM
# StartServers: number of server processes to start
# MinSpareServers: minimum number of server processes which are kept spare
# MaxSpareServers: maximum number of server processes which are kept spare
# MaxClients: maximum number of server processes allowed to start
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule mpm_prefork_module>
StartServers 	40
MinSpareServers 	20
MaxSpareServers 	80
ServerLimit	 	200
MaxClients 	200
MaxRequestsPerChild	1000
</IfModule>

# worker MPM
# StartServers: initial number of server processes to start
# MaxClients: maximum number of simultaneous client connections
# MinSpareThreads: minimum number of worker threads which are kept spare
# MaxSpareThreads: maximum number of worker threads which are kept spare
# ThreadsPerChild: constant number of worker threads in each server process
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule mpm_worker_module>
StartServers 	10
ServerLimit 	1000
MaxClients 	1000
MinSpareThreads 	25
MaxSpareThreads 	75 
ThreadsPerChild 	25
MaxRequestsPerChild 0
</IfModule>

# BeOS MPM
# StartThreads: how many threads do we initially spawn?
# MaxClients: max number of threads we can have (1 thread == 1 client)
# MaxRequestsPerThread: maximum number of requests each thread will process
<IfModule mpm_beos_module>
StartThreads 	10
MaxClients 	100
MaxRequestsPerThread 10000
</IfModule>

# NetWare MPM
# ThreadStackSize: Stack size allocated for each worker thread
# StartThreads: Number of worker threads launched at server startup
# MinSpareThreads: Minimum number of idle threads, to handle request spikes
# MaxSpareThreads: Maximum number of idle threads
# MaxThreads: Maximum number of worker threads alive at the same time
# MaxRequestsPerChild: Maximum number of requests a thread serves. It is 
# 	recommended that the default value of 0 be set for this
# 	directive on NetWare. This will allow the thread to 
# 	continue to service requests indefinitely. 	
<IfModule mpm_netware_module>
ThreadStackSize 	65536
StartThreads 	250
MinSpareThreads 	25
MaxSpareThreads 	250
MaxThreads 	1000
MaxRequestsPerChild 	0
MaxMemFree 	100
</IfModule>

# OS/2 MPM
# StartServers: Number of server processes to maintain
# MinSpareThreads: Minimum number of idle threads per process, 
# 	to handle request spikes
# MaxSpareThreads: Maximum number of idle threads per process
# MaxRequestsPerChild: Maximum number of connections per server process
<IfModule mpm_mpmt_os2_module>
StartServers 	2
MinSpareThreads 	5
MaxSpareThreads 	10
MaxRequestsPerChild	0
</IfModule>

[krdc.pl 91]

Cpu(s): 24.0%us, 12.4%sy, 0.0%ni, 0.0%id, 61.2%wait

 

 

czeka na operacja I/O - pi*oko = niewyrabia dysk

[Gość N3T5kY]

httpd -V

 

I pokaż cały konfig apacza.

Oraz

 

du -h /var/lib/mysql

[mrjozo 0]

Server version: Apache/2.2.14 (Unix)
Server built: Jan 2 2010 11:54:35
Server's Module Magic Number: 20051115:23
Server loaded: APR 1.3.9, APR-Util 1.3.9
Compiled using: APR 1.3.9, APR-Util 1.3.9
Architecture: 32-bit
Server MPM: 	Prefork
threaded: 	no
forked: 	yes (variable process count)
Server compiled with....
-D APACHE_MPM_DIR="server/mpm/prefork"
-D APR_HAS_SENDFILE
-D APR_HAS_MMAP
-D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
-D APR_USE_SYSVSEM_SERIALIZE
-D APR_USE_PTHREAD_SERIALIZE
-D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
-D APR_HAS_OTHER_CHILD
-D AP_HAVE_RELIABLE_PIPED_LOGS
-D DYNAMIC_MODULE_LIMIT=128
-D HTTPD_ROOT="/etc/httpd"
-D SUEXEC_BIN="/usr/sbin/suexec"
-D DEFAULT_PIDLOG="/var/logs/httpd.pid"
-D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
-D DEFAULT_LOCKFILE="/var/logs/accept.lock"
-D DEFAULT_ERRORLOG="logs/error_log"
-D AP_TYPES_CONFIG_FILE="conf/mime.types"
-D SERVER_CONFIG_FILE="conf/httpd.conf"

 

du -h /usr/lib/mysql
14M 	/usr/lib/mysql

 

widzę właśnie że dysk nie wyrabia ale strona która doszła ma max 1,5k uu/10k odsłon/ dobe i 40 osób online... chyba że ta joomla jest taka koszmarna

[Gość N3T5kY]

A masz w joomli jakieś moduły do statystyk ?

[mrjozo 0]

Wszystko wyłączone, są dodatki poinstalowane bo to rozbudowany serwis i jest xcache ale to jednak ona bo po wyłączeniu serwisu load spada na 0.2

[Gość N3T5kY]

Sprawdź wszystkie dodatki, czy czegoś nie logują (do bazy) itp.

Ja miałem podobny problem na Joomli (jako że jest to i7-2t, więc gładko poszło) - komponent odpowiedzialny za statystyki ładował wszystko do mysqla, a jako że odwiedzin było dość sporo - ok. 10k/h, sprawiało to duży problem

[mrjozo 0]

Po głębszym namyśle nie pozostaje mi chyba nic innego jak nowy serwer:

http://www.webhostingtalk.pl/topic/22535-zlece-transfer-config/