[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: How to improve performance with MDB backend?



SaÅa-Stjepan BakÅa wrote:
First test with your sugestions.
I am using Phyton program writen by me to add data to server.
Server is Centos 6.2 based (hardware described in my first post)
Python runs on separeate dual core PC with 1Gb connection to servers.
Servers are configured as N-way Multymaster

Test start    Test stop     Test duration          Num users    User/sec

19.4.2013   19.4.2013      sec 7789,00         1000000        128,39
11:53:45     14:03:34        min 129,8166667

Database location mounted as:
UUID=616c291a-7fe4-47a1-87d1-c221a8e1c4f8 /opt                    ext4
noatime,auto    1 2

vm.dirty_ratio = 90
vm.dirty_expire_centisecs = 60000

Scheduler is:
[root@spr1 ~]# cat /sys/block/sda/queue/scheduler
noop anticipatory deadline [cfq]

memory manager libhoard.so (latest from hoard site)

You really need to learn something more about system administration; you clearly don't know what to investigate but this is all fundamental sysadmin knowledge.

First things first - when something is "slow" - what exactly is slow? Is it using excessive CPU time? Is it waiting for disk I/O? Every sysadmin should automatically ask this question first of all, and every sysadmin should know how to tell the difference. If you don't know these things then you are not qualified to be a sysadmin and need to go get training. This is not the forum for teaching you these things.

Copy/pasting someone else's VM tuning settings without understanding what they mean or why they are being set is "cargo cult sysadmin". It is wrong and nobody on this list / in this community should be encouraging it. Quick easy spoonfed answers don't actually help understanding, and understanding is the only real way forward.

In particular, VM tuning settings are highly OS dependent, and probably kernel version dependent too. Good settings depend on exactly what your own system contains; settings that work for someone else may be useless or worse on your own setup.

Simple answers have narrow relevance that gets obsolete quickly. Learning how to think and investigate problems is knowledge that serves you the rest of your life.

As a starting point - what does vmstat tell you? Don't just paste its output here, learn what it means.

--
  -- Howard Chu
  CTO, Symas Corp.           http://www.symas.com
  Director, Highland Sun     http://highlandsun.com/hyc/
  Chief Architect, OpenLDAP  http://www.openldap.org/project/