Bug 521637 - Upgrade to kernel-2.6.30.5-43.fc11.x86_64 drastically slows 389 DS response time
Summary: Upgrade to kernel-2.6.30.5-43.fc11.x86_64 drastically slows 389 DS response time
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: 389
Classification: Retired
Component: Performance
Version: 1.2.1
Hardware: x86_64
OS: Linux
low
urgent
Target Milestone: ---
Assignee: Rich Megginson
QA Contact: Chandrasekar Kannan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-09-07 11:27 UTC by Anthony Messina
Modified: 2015-01-04 23:40 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-01-18 23:07:25 UTC
Embargoed:


Attachments (Terms of Use)
Cacti graph showing response time increase with kernel change (46.28 KB, image/png)
2009-09-07 11:27 UTC, Anthony Messina
no flags Details

Description Anthony Messina 2009-09-07 11:27:31 UTC
Created attachment 359984 [details]
Cacti graph showing response time increase with kernel change

After upgrading to kernel-2.6.30.5-43.fc11.x86_64, I noticed that 389 DS' performance/responsiveness was horrible!  I also noticed, using Cacti that the time for a query response was drastically increased.

When I downgrade to kernel-2.6.29.6-217.2.16.fc11.x86_64, the problem goes away completely.

I am reporting this here as I cannot tell what part of the kernel changes would affect this.

For what it's worth, I have also followed the steps to debug outlined in https://bugzilla.redhat.com/show_bug.cgi?id=516611#c6 as I try to work out that issue, though I haven't been able to reproduce a crash yet for that one.

I have attached the Cacti graph to show what happened.

389-admin-1.1.8-4.fc11.x86_64
389-admin-console-1.1.4-1.fc11.noarch
389-admin-console-doc-1.1.4-1.fc11.noarch
389-adminutil-1.1.8-3.fc11.x86_64
389-console-1.1.3-3.fc11.noarch
389-ds-1.1.3-4.fc11.noarch
389-ds-base-1.2.2-1.fc11.x86_64
389-ds-base-debuginfo-1.2.1-1.fc11.x86_64
389-ds-console-1.2.0-4.fc11.noarch
389-ds-console-doc-1.2.0-4.fc11.noarch
389-dsgw-1.1.4-1.fc11.x86_64

Comment 1 Anthony Messina 2009-10-02 04:04:20 UTC
This issue does not seem to occur after upgrading to kernel-2.6.30.8-64.fc11.x86_64


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