Bug 76296 - Amount of CPU % to different processes is wrong.
Summary: Amount of CPU % to different processes is wrong.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 8.0
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-10-19 14:27 UTC by Ivo Sarak
Modified: 2008-08-01 16:22 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-09-30 15:40:05 UTC
Embargoed:


Attachments (Terms of Use)

Description Ivo Sarak 2002-10-19 14:27:34 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020827

Description of problem:
Process with higher priority does not get more CPU power.

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


How reproducible:
Always

Steps to Reproduce:
I run two different Distributed projects: FAH and EON.
	

Actual Results:  Both are getting equal amount of CPU power.

Expected Results:  FahCore_78.exe 75% of CPU power and EON_client 25% of CPU power.

Additional info:

http://www.vendomar.ee/~ivo/priorities.png

$ uname -a
Linux hareba 2.4.18-14 #1 Wed Sep 4 12:13:11 EDT 2002 i686 athlon i386 GNU/Linux

Comment 1 Ivo Sarak 2002-10-25 17:11:25 UTC
Strange but on the same system with the same priority set, different core will
act  differently:
http://www.vendomar.ee/~ivo/priorities1.png

Comment 2 Bugzilla owner 2004-09-30 15:40:05 UTC
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
persists.

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/



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