Issue 67414 - OpenOffice applications use only one processor
Summary: OpenOffice applications use only one processor
Status: CONFIRMED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 2.0.3
Hardware: PC Windows XP
: P3 Trivial with 1 vote (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
: 127405 (view as issue list)
Depends on:
Blocks:
 
Reported: 2006-07-15 20:06 UTC by cphilipp
Modified: 2017-05-06 06:45 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description cphilipp 2006-07-15 20:06:52 UTC
Hi,

sorry, if this is the wrong project / subcomponent; it's only a guess.

My observation with OpenOffice calc application is that it does not use dual
core processors and I would assume, it will not use multi processors either.
I have a dual core Athlon X2 4200+, but when running OpenOffice calc, the CPU
load  never gets beyond 50% (Of course both cores are involved, this is due to
the OS and the scheduling policy, but both together sum up to 50% or below).

I would assume, this is also true for other applications, so I put this issue to
the framework project.

It would be nice to use the full computing power at your hand, especially for
long running operations in calc like recalculating a huge spreadsheet. I know
changing the application to multi threaded is not easy and requires new
algorithms if applied to an operation like calculation.

But as dual cores / quad cores become more and more standard, it will be necessary.

At least this would allow to run more then one document in parallel, when one is
doing recalculation, the other window still will be usable and reacting. Which
is not the case in the moment. Loading a spreadsheet will block all other
spreadsheet windows open already.
Comment 1 Olaf Felka 2006-07-17 08:40:01 UTC
reassigned
Comment 2 Marcus 2017-05-06 06:45:53 UTC
*** Issue 127405 has been marked as a duplicate of this issue. ***