Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 235165 - Poor performance of openldap with RHEL 3,4,5 on HP DL380 G4 and G5
Summary: Poor performance of openldap with RHEL 3,4,5 on HP DL380 G4 and G5
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: openldap
Version: 4.0
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
: ---
Assignee: Jan Zeleny
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-04-04 06:01 UTC by Ching-Che Yen
Modified: 2010-02-22 13:08 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-02-22 13:08:08 UTC


Attachments (Terms of Use)

Description Ching-Che Yen 2007-04-04 06:01:26 UTC
Description of problem:

I have posted another Bug:

Bugzilla Bug 234801: openldap got poor performance with RHEL5 on HP DL380 G4 and G5

After testing further,I found that all openldap with RHEL3,4,5 could just handle
about 4~12 authentication queries per second.
And then I tested Fedora Core6 ,It's the same performance.

I wonder that is there anyone who had the same problem with HP DL380 or other
hardware platform?

Thank you very much and sorry for my poor english.

Comment 1 Jan Zeleny 2010-02-22 13:08:08 UTC
As I wrote in the referenced bug, I need more information regarding this. Also this bug is filed for RHEL4 and RHEL5 is presented as the main system with this issue in the description. I'm closing this bug for insufficient data. If the issue persists with latest RHEL5, please contact out technical support, which can help with solving this issue or gathering more data needed to fix this.


Note You need to log in before you can comment on or make changes to this bug.