back_wt benchmark

Benchmarking OpenLDAP WiredTiger backend

Scenarios

LDAP ADD Benchmarking

Add 10000 entries with some concurrency levels.

LDAP SEARCH Benchmarking

Search 100000 times with random filters.

filter range:

"(cn=user1)" ... "(cn=user10000)"

LDAP BIND Benchmarking

Bind 100000 times with random dn.

dn range:

cn=user1,dc=example,dc=com ... cn=user10000,dc=example,dc=com

Results

LDAP ADD Throughput

Concurrency	back-bdb	back-wt
1	77.48	1653.65
2	77.54	3315.00
4	76.75	6582.71
8	72.06	10248.39
16	75.56	11833.70
32	74.41	12630.06
64	80.33	10741.02

LDAP SEARCH Throughput

Concurrency	back-bdb	back-wt
1	2766.32	2006.42
2	5418.93	4223.38
4	8303.61	7746.50
8	9247.05	9351.27
16	11582.60	10501.93
32	10552.11	9456.37
64	11381.98	11414.41

LDAP BIND Throughput

Concurrency	back-bdb	back-wt
1	3547.97	3176.62
2	7800.54	7256.41
4	9666.20	9319.00
8	8759.90	9800.08
16	7736.12	8832.02
32	8818.28	8159.96
64	7891.34	8941.11

Enviroment

Hardware

• Model: PowerEdge R710
• CPU: Xeon X5650(12 cores)
• Memory: 50G
• Disk: SAS 15,000 RPM

Software Version

• OpenLDAP 2.4.40 with back-wt patch
• BerkeleyDB 5.3.28
• WiredTiger 2.5

Benchmarking tool

• lb

Configration

• back-bdb slapd.conf

threads 64

database bdb
cachesize 100000
idlcachesize 300000

dbconfig set_cachesize 1 0 1
dbconfig set_lg_bsize 10485760
dbconfig set_lk_max_objects 5000
dbconfig set_lk_max_locks 5000
dbconfig set_lk_max_lockers 5000

index objectClass pres,eq
index cn          pres,eq

• back-wt slapd.conf

threads 64

database wt
wtconfig create,cache_size=1000M
index objectClass pres,eq
index cn          pres,eq