#203 SLAMD Mixed Load Scalability - Large Entry/DB
Opened 8 years ago by rmeggins. Modified 2 months ago

https://bugzilla.redhat.com/show_bug.cgi?id=587937

Description of problem:
Performance degrade 51000 ops (search only) to 5000 ops (5 million entries),
and 2200 ops (25 million entries) as:
a. DB size increases (5 to 25 millions entries)
b. Mixed load is introduced ([Add,Bind,Compare,Delete,Modify,Modify DN, Search]
= [1,28,0,1,7,0,64])

Other observations:

a/ Writes increases over time
b/ 50KB IO per transaction

Version-Release number of selected component (if applicable):

        Red Hat-Directory/8.1.0 B2010.07.218

How reproducible:
Very


Steps to Reproduce:
1. Set up SLAMD
2. Use Mixed Load
3. Compare results

Actual results:

See attachements

Expected results:


Additional info:

batch update moving tickets to future

set default ticket origin to Community

Added initial screened field value.

Metadata Update from @rmeggins:
- Issue set to the milestone: 1.4 backlog

3 years ago

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to None (was: Needs Review)
- Issue close_status updated to: None
- Issue tagged with: Performance

2 months ago

Login to comment on this ticket.

Metadata