Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 232223 - [ui] consider lowering job priority of IU sizing job
Summary: [ui] consider lowering job priority of IU sizing job
Status: RESOLVED WONTFIX
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: p2 (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: P2 Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 225759
Blocks:
  Show dependency tree
 
Reported: 2008-05-15 00:09 EDT by Susan McCourt CLA
Modified: 2020-02-21 00:58 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Susan McCourt CLA 2008-05-15 00:09:00 EDT 
It seems like the sizing job inside a wizard is still really impacting the performance of the operation that the wizard is trying to launch.  At least in my workspace, where it is getting connection timeouts with an artifact repo.

I'm wondering if the sizing job should be reduced to priority Job.DECORATE.  This would actually kind of make sense since the size info is not crucial, especially after the user has decided to proceed.  (We try to cancel the sizing job, but it doesn't really respond to progress monitor cancelling, especially if it is timing out on a connection.)
Comment 1 Susan McCourt CLA 2008-05-15 00:11:04 EDT 
marking RC1 as this might be a one-liner that could really help things.  Will investigate.
Comment 2 Susan McCourt CLA 2008-05-15 11:32:04 EDT 
The priority really should be Job.DECORATE, as the definition for this priority matches exactly with our situation...info the user may be interested in but is not waiting for.  However, I tried it and it didn't make any noticeable difference in the scenarios where I was seeing problems, so it's not an RC1 kind of change.
Comment 3 John Arthorne CLA 2008-05-15 13:20:48 EDT 
Yes, job priorities don't have a huge impact. They affect what order jobs start in, but once the job is running it has no effect. If there are idle worker threads and the job wait queue is empty, the job will be scheduled immediately regardless of priority.
Comment 4 Susan McCourt CLA 2008-10-20 14:40:15 EDT 
moving to M4 to work while working bug 250862
Comment 5 Susan McCourt CLA 2008-12-04 14:15:56 EST 
The performance here is much improved since I opened this bug.  
In bug #240055, it is suggested that the sizing info is useless because it is not immediate, so I don't see decreasing the prio.  

I don't see doing anything more specific here in the near term so removing milestone.
Comment 6 Susan McCourt CLA 2009-07-09 17:08:22 EDT 
bulk update:  UI bugs not yet assigned a milestone are returned to the inbox.
Comment 7 Eclipse Webmaster CLA 2019-09-06 15:32:50 EDT 
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.
Comment 8 Ed Merks CLA 2020-02-21 00:58:20 EST 
I don't think this is needed (and I don't know where it's needed).