Bug 305717 - Investigate storing resource tree snapshots in ZIP format
Summary: Investigate storing resource tree snapshots in ZIP format
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 3.5   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: performance
Depends on: 306573
Blocks:
  Show dependency tree
 
Reported: 2010-03-12 13:24 EST by Martin Oberhuber CLA
Modified: 2019-09-06 16:06 EDT (History)
2 users (show)

See Also:

Attachments
Dirty hack for fast project snapshots to be un-compressed and not copied (5.99 KB, patch)
2010-04-14 15:25 EDT, Martin Oberhuber CLA 		no flags Details | Diff
View All 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 Martin Oberhuber CLA 2010-03-12 13:24:57 EST 
+++ This bug was initially created as a clone of Bug #301563 +++

As per bug 301563 comment 48, saving resource .tree snapshots in ZIP format may be a low-hanging-fruit simple improvement improve performance on project re-open, reduce data storage in workspace metadata, and simplify the code for bug 301563.

We should investigate this and measure performance impact.
Comment 1 Martin Oberhuber CLA 2010-04-14 15:25:00 EDT 
Created attachment 164879 [details]
Dirty hack for fast project snapshots to be un-compressed and not copied

Attached is a quick and dirty hack for experimenting with ZIPped versus non-zipped resource tree snapshots: It changes the snapshot save and load code to
  (a) not copy the saved snapshot on import, but open directly from the 
      given location, and
  (b) not save/load in ZIP format but handle uncompressed.

Initial measurements didn't really show much difference, but this may be worth investigating again in due time.
Comment 2 Martin Oberhuber CLA 2010-04-14 15:27:31 EDT 
See also bug 306573 comment 2.
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:06:15 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.