Bug 66371 - [History] History Store "max states" policy enforcement
Summary: [History] History Store "max states" policy enforcement
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 55182
  Show dependency tree
 
Reported: 2004-06-09 14:28 EDT by DJ Houghton CLA
Modified: 2019-09-06 16:16 EDT (History)
2 users (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 DJ Houghton CLA 2004-06-09 14:28:21 EDT 
build i0608-0800

During #shutdown of the history store, we iterate over all the entries and trim
the file states based on the preference value for MAX_STATES.

We are considering changing the shutdown method so we don't have to iterate over
the history store entries. If this is the case, then we need to change when this
policy is enforced.
Comment 1 DJ Houghton CLA 2004-06-18 10:29:04 EDT 
We've made some performance improvements for shutdown for 3.0.
Investigate this for 3.1.
Comment 2 John Arthorne CLA 2005-02-24 12:21:49 EST 
Rafael, is this bug obsolete with the new history store implementation?
Comment 3 Rafael Chaves CLA 2005-02-24 12:46:31 EST 
No, we still do that. But clearining the history is much less expensive with the
new implementation. Depending on the outcome of bug 55182, looks like a wontfix
to me.
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:16:57 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.