Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 320945

Summary: [Progress] jsp files opened and progress view use CPU 30% - 40%
Product: [Eclipse Project] Platform Reporter: alfredo
Component: UIAssignee: Platform UI Triaged <platform-ui-triaged>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: kazm, krzysztof.daniel, sarika.sinha, thatnitind
Version: 3.4.2Keywords: performance
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug
Attachments:
Description Flags
Attaching the screenshot of yourkit to show how the Progress View is consuming time to update the toolbar values. none

Description alfredo CLA 2010-07-26 14:11:56 EDT 
Build Identifier: Eclipse 3.4         

This behaviour is seen on RAD 7.5.5.1 which is based on Eclipse 3.4


In Progress View,  “Show sleeping and system operations” checked and  Jsp editor open (5-10+ jsp files) 
This causes the cpu to cycle from 5% to 30 % (slows down work considerably – this behavior is the same for any length file, I tested 5 to 500 lines) 


In progress view “Show sleeping and system operations” un-checked and  Jsp editor open  (5-10+) – 
This causes the cpu to cycle from 3% to 8% (not really much of a problem but notable and potentially an indication of a runaway process in the JSP Editor – 
this behavior is only slightly worse for longer files 5% to 9% cpu, I tested 5 to 500 lines). 




Reproducible: Always

Steps to Reproduce:
1.Open  5 to 10 JSP files with 5 to 500 lines
2.Open Progress view
3.In Preferences for Progress View, check 'Show sleeping and system operations'
Comment 1 alfredo CLA 2010-07-26 14:16:56 EDT 
Created attachment 175254 [details]
Attaching the screenshot of yourkit to show how the Progress View is consuming time to update the toolbar values. 

Attaching the screenshot of yourkit to show how the Progress View is consuming time to update the toolbar values.
Comment 2 alfredo CLA 2010-07-26 14:18:01 EDT 
Source Editor does not  start and stop the DirtyRegion Job on each key strok but keeps it running in the sleeping mode.SSe DirtyRegion job is not consuming CPU but in Progress View , if 5 JSPs are open all the 5 jobs are always running and the way eclipse Platform has implemented Progress view it shoots up the CPU.
Comment 3 Krzysztof Daniel CLA 2010-07-27 05:38:43 EDT 
(In reply to comment #2)
> Source Editor does not  start and stop the DirtyRegion Job on each key strok
> but keeps it running in the sleeping mode.SSe DirtyRegion job is not consuming
> CPU but in Progress View , if 5 JSPs are open all the 5 jobs are always running
> and the way eclipse Platform has implemented Progress view it shoots up the
> CPU.

The sleeping mode means actually that either job has been put into a sleep or a job has been sheduled to be run after certain amount of time. I have not looked into the source code, but I expect that this jobs schedules itself very often and therefore generates heavy traffic in progress view.
Comment 4 Lars Vogel CLA 2019-11-14 03:43:09 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.