Nie jesteś zalogowany.
Jeśli nie posiadasz konta, zarejestruj je już teraz! Pozwoli Ci ono w pełni korzystać z naszego serwisu. Spamerom dziękujemy!
Prosimy o pomoc dla małej Julki — przekaż 1% podatku na Fundacji Dzieciom zdazyć z Pomocą.
Więcej informacji na dug.net.pl/pomagamy/.
Witam,
Mam serwerek Xeon X5650, 12GB ramu. Chodzi na nim serwer gier HLDS. Kernel debianowy defaultowy nie byl 1000hz wiec bylem zmuszony do rekompilacji. Na serwerze co 10min pojawiają się 2-7sek lagi jakby wtyka eth poszla w diably ;-) I potem znow wraca do normy.
Za cholere nie wime co to może być. Może macie jakieś koncepcje?
root@hyyc:/# mii-tool eth0 SIOCGMIIREG on eth0 failed: Input/output error SIOCGMIIREG on eth0 failed: Input/output error eth0: negotiated 100baseTx-FD, link ok root@hyyc:/# ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Full Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on MDI-X: off Supports Wake-on: pumbag Wake-on: g Current message level: 0x00000001 (1) Link detected: yes
Może coś z sieciówką? Albo jakas opcja kernela?
W kernelu zmienialem jeszcze przez syscrl:
net.ipv4.tcp_fin_timeout = 25 net.ipv4.tcp_keepalive_time = 1800 net.ipv4.tcp_window_scaling = 0 net.ipv4.tcp_sack = 0 net.ipv4.tcp_timestamps = 0
Powoli kończą się pomysły.. a serwer laguje mimo ze jest mocny.. Jakieś koncepcje?
Sieciówke mam jako moduł w kernelu. I są tam 2 takie same karty sieciowe. Myślałem, że może kabel. zrekonifgurowałem interfejsy, przepiełem jednak nie ma poprawy [; Pamięc w użyciu to połowa dostępnej pamięci czyli 6GB. Serwer to xeon 2.67 24cory, 12GB ramu.
Poniżej link do 5Mb pliku tekstowego z zawierającego wyniki:
IOSTAT="iostat -xtc 1 1800"
MPSTAT="mpstat -P ALL 1 1800"
VMSTAT="vmstat 1 1800"
http://www15.speedyshare.com/files/25704035/downloa … 010-12-14.txt
Może ktoś będzie w stanie coś doradzić? Mi to wygląda na problemy z prockiem, albo dyskiem. Choć dysk hdparmem checkniety nie wykazuje błędów, i wszystko naturalnie. Hmm ....
Ostatnio edytowany przez Grzeslaw (2010-12-14 17:13:37)
Offline
hej,
pokaż wynik
ifconfig ethtool -S eth0 cat /proc/interrupts
Jaki ethernetów używasz ? Jakie karty ? Pokaż
lspci
Jaki kernel
uname -a
I jeszcze jakich systemów plików używasz :)
Ostatnio edytowany przez zielkam (2010-12-14 20:24:19)
Offline
Na dyskach jest RAID. Kernela kompilowałem sam, ale problem występuje też na dystrybucyjnym...
root@shoot2:~# uname -a Linux shoot2 2.6.36.1 #1 SMP Fri Dec 10 17:29:39 CET 2010 x86_64 GNU/Linux root@shoot2:~# lspci 00:00.0 Host bridge: Intel Corporation 5500 I/O Hub to ESI Port (rev 13) 00:01.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 (rev 13) 00:03.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 (rev 13) 00:07.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 7 (rev 13) 00:08.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 8 (rev 13) 00:09.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 9 (rev 13) 00:0a.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 10 (rev 13) 00:13.0 PIC: Intel Corporation 5520/5500/X58 I/O Hub I/OxAPIC Interrupt Controller (rev 13) 00:14.0 PIC: Intel Corporation 5520/5500/X58 I/O Hub System Management Registers (rev 13) 00:14.1 PIC: Intel Corporation 5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers (rev 13) 00:14.2 PIC: Intel Corporation 5520/5500/X58 I/O Hub Control Status and RAS Registers (rev 13) 00:14.3 PIC: Intel Corporation 5520/5500/X58 I/O Hub Throttle Registers (rev 13) 00:16.0 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 13) 00:16.1 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 13) 00:16.2 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 13) 00:16.3 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 13) 00:16.4 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 13) 00:16.5 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 13) 00:16.6 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 13) 00:16.7 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 13) 00:1a.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4 00:1a.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5 00:1a.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6 00:1a.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2 00:1c.0 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 1 00:1c.4 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 5 00:1c.5 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 6 00:1d.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #1 00:1d.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #2 00:1d.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #3 00:1d.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #1 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90) 00:1f.0 ISA bridge: Intel Corporation 82801JIR (ICH10R) LPC Interface Controller 00:1f.2 SATA controller: Intel Corporation 82801JI (ICH10 Family) SATA AHCI Controller 00:1f.3 SMBus: Intel Corporation 82801JI (ICH10 Family) SMBus Controller 01:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 10) 02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection 03:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection root@shoot2:~# ethtool -S eth0 NIC statistics: rx_packets: 101465184 tx_packets: 106664855 rx_bytes: 8447367868 tx_bytes: 16870391597 rx_broadcast: 278134 tx_broadcast: 0 rx_multicast: 0 tx_multicast: 6 rx_errors: 0 tx_errors: 0 tx_dropped: 0 multicast: 0 collisions: 0 rx_length_errors: 0 rx_over_errors: 0 rx_crc_errors: 0 rx_frame_errors: 0 rx_no_buffer_count: 0 rx_missed_errors: 0 tx_aborted_errors: 0 tx_carrier_errors: 0 tx_fifo_errors: 0 tx_heartbeat_errors: 0 tx_window_errors: 0 tx_abort_late_coll: 0 tx_deferred_ok: 0 tx_single_coll_ok: 0 tx_multi_coll_ok: 0 tx_timeout_count: 0 tx_restart_queue: 20 rx_long_length_errors: 0 rx_short_length_errors: 0 rx_align_errors: 0 tx_tcp_seg_good: 0 tx_tcp_seg_failed: 0 rx_flow_control_xon: 0 rx_flow_control_xoff: 0 tx_flow_control_xon: 0 tx_flow_control_xoff: 0 rx_long_byte_count: 8447367868 rx_csum_offload_good: 99788365 rx_csum_offload_errors: 117 rx_header_split: 0 alloc_rx_buff_failed: 0 tx_smbus: 0 rx_smbus: 0 dropped_smbus: 0 rx_dma_failed: 0 tx_dma_failed: 0 root@shoot2:~# root@shoot2:~# cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath] [faulty] md2 : active raid1 sda3[0] sdb3[1] 472760184 blocks super 1.2 [2/2] [UU] md1 : active raid1 sda2[0] sdb2[1] 976884 blocks super 1.2 [2/2] [UU] md0 : active raid1 sda1[0] sdb1[1] 14646200 blocks super 1.2 [2/2] [UU] unused devices: <none> root@shoot2:~# fdisk -l Disk /dev/sda: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000debbc Device Boot Start End Blocks Id System /dev/sda1 * 1 1824 14647296 fd Linux raid autodetect /dev/sda2 1824 1946 976896 fd Linux raid autodetect /dev/sda3 1946 60802 472761344 fd Linux raid autodetect Disk /dev/sdb: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000e88ab Device Boot Start End Blocks Id System /dev/sdb1 * 1 1824 14647296 fd Linux raid autodetect /dev/sdb2 1824 1946 976896 fd Linux raid autodetect /dev/sdb3 1946 60802 472761344 fd Linux raid autodetect Disk /dev/md0: 15.0 GB, 14997708800 bytes 2 heads, 4 sectors/track, 3661550 cylinders Units = cylinders of 8 * 512 = 4096 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Disk /dev/md0 doesn't contain a valid partition table Disk /dev/md1: 1000 MB, 1000329216 bytes 2 heads, 4 sectors/track, 244221 cylinders Units = cylinders of 8 * 512 = 4096 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Disk /dev/md1 doesn't contain a valid partition table Disk /dev/md2: 484.1 GB, 484106428416 bytes 2 heads, 4 sectors/track, 118190046 cylinders Units = cylinders of 8 * 512 = 4096 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Disk /dev/md2 doesn't contain a valid partition table root@shoot2:~# hdparm -t /dev/sda /dev/sda: Timing buffered disk reads: 306 MB in 3.01 seconds = 101.82 MB/sec root@hoot2:~# hdparm -t /dev/sdb /dev/sdb: Timing buffered disk reads: 234 MB in 3.02 seconds = 77.43 MB/sec root@niceshoot2:~# hdparm -T /dev/sda /dev/sda: Timing cached reads: 16490 MB in 2.00 seconds = 8254.15 MB/sec root@niceshoot2:~# hdparm -T /dev/sdb /dev/sdb: Timing cached reads: 16876 MB in 2.00 seconds = 8447.67 MB/sec
--- EDIT
Okazuje się, że lagi występują w przypadku gdy wykonywane jest kopiowanie danych na serwerze, czyli wygląda na coś z dyskiem ... Ale jak widać, z dyskiem wszystko okey. Dlatego też zagatka ...
Ostatnio edytowany przez Grzeslaw (2010-12-17 14:15:51)
Offline
Spróbuj z innym filesystemem. W moim przypadku pisanie logów z aplikacji powoduje tak duże obciążenie systemu, że aplikacja laguje. Zaczynam wszędzie stosować xfs`a, bo ext* i inne tego typu w takich wypadkach wypadają krucho.
Offline