Notice
Recent Posts
Recent Comments
Link
일 | 월 | 화 | 수 | 목 | 금 | 토 |
---|---|---|---|---|---|---|
1 | 2 | 3 | 4 | |||
5 | 6 | 7 | 8 | 9 | 10 | 11 |
12 | 13 | 14 | 15 | 16 | 17 | 18 |
19 | 20 | 21 | 22 | 23 | 24 | 25 |
26 | 27 | 28 | 29 | 30 | 31 |
Tags
- goaccess
- Linux
- http
- Kernel
- 솔라리스
- Performance
- rsync
- PORT
- Python
- CPU
- 디스크
- pid
- rm
- rm -rf
- 좌절교육
- ext4
- PERL
- DNS
- Disk
- Cache
- cadre
- apachetop
- ext3
- 쇼펜의상속자 #킨텍스메가쇼 #섬유향수탈취제
- Hack
- 리눅스
- Bash
- 칭찬교육
- iptables
- windows
Archives
- Today
- Total
목록리눅스/pgsql (1)
Ben's
postgresql performance
http://archives.postgresql.org/pgsql-performance/2009-06/msg00319.php I see a lot of io wait time there. My guess is that your DB is flooded with synchronous writes. IF you want to optimize the hardware for this you have a couple options. I'm assuming your RAID 0 is not hardware RAID. 1. Use 8.3+ and asynchronous commit (set synchronous_commit=false). This is safe data wise, but if your DB crash..
리눅스/pgsql
2013. 1. 21. 15:06