Issue 20270 - Q-PCD Performance-1 [Scalability]
Summary: Q-PCD Performance-1 [Scalability]
Status: ACCEPTED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 1.1
Hardware: All All
: P4 Trivial (vote)
Target Milestone: AOO Later
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-09-28 14:26 UTC by matthias.huetsch
Modified: 2013-02-07 22:13 UTC (History)
1 user (show)

See Also:
Issue Type: FEATURE
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description matthias.huetsch 2003-09-28 14:26:16 UTC
Source
Enterprise customers

Category
Client/Server

Customer Need/Problem
Faster system responsiveness over large scale deployments.

Product Requirement 
Scalability improvements, better sharing of resources.

Comment
Most issues addressed in Geordi.

Eng Effort
-

Eng Owner
Matthias Huetsch

Product Concept
The most urgent issue -- an excessive number of voluntary context switches per
second -- is addressed in Geordi, but further improvements can be achieved in
the following areas:

1) Replace current timer based concepts -- in particular the concept of an  idle
timer -- by event driven concepts, to further reduce the number of unnecessary
voluntary context switches.

2) Replace current assumption of cooperative multitasking or green threads with
the requirement of preemptive or native threads multitasking, to further reduce
the number of voluntary context switches.

3) Reduce amount and size of writeable data segments in shared libraries, to
reduce the amount of non-shareable private memory per process.

Functional Specification
-
Comment 1 matthias.huetsch 2003-09-28 14:28:34 UTC
Accepting...
Comment 2 matthias.huetsch 2003-09-28 14:35:51 UTC
accepting, really,...
Comment 3 lutz.hoeger 2003-10-23 07:44:06 UTC
added keyword Q-PCD
Comment 4 matthias.huetsch 2004-04-25 16:02:17 UTC
The remaining scalability issues have been re-evaluated as being of a broader
scope than anticipated, and have been re-prioritized in favor of other issues.
They might be revisited on an individual base, or in a later release.
Comment 5 Martin Hollmichel 2004-05-28 15:11:20 UTC
according to the announcement on releases
(http://www.openoffice.org/servlets/ReadMsg?list=releases&msgNo=7503) this issue
will be re-targeted to OOo Later.