This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 240915 - huge repository size (140Gb) during xRef checks
Summary: huge repository size (140Gb) during xRef checks
Status: RESOLVED FIXED
Alias: None
Product: cnd
Classification: Unclassified
Component: Code Model (show other bugs)
Version: 8.0
Hardware: All All
: P2 normal (vote)
Assignee: Maria Tishkova
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-24 08:55 UTC by Vladimir Voskresensky
Modified: 2014-01-31 02:39 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir Voskresensky 2014-01-24 08:55:02 UTC
tried to run "show errors HL" or "xRef perf" for LLVM project and repository became 140Gb
Comment 1 Maria Tishkova 2014-01-29 16:31:06 UTC
fixed in http://hg.netbeans.org/cnd-main/rev/991972714aef

Introduced another maintenance mechanism:
1) during write to the DoubleFileStrorage if size of one of the files (active or passive)
is more than 512 Mb we will invoke defragment method
2) when defragment is invoked we will move data from passive to active file for one iteration (means we ignore maintenance interval)
Comment 2 Maria Tishkova 2014-01-30 14:07:37 UTC
additional fix:
http://hg.netbeans.org/cnd-main/rev/37168ccb88f5 
increase threshold on 256Mb if fragmentation percentage is less than 40
Comment 3 Vladimir Voskresensky 2014-01-30 16:41:16 UTC
http://hg.netbeans.org/cnd-main/rev/1bcd0b4b99d5
- own "big file size" per storage instance, not one for all storages
Comment 4 Quality Engineering 2014-01-31 02:39:59 UTC
Integrated into 'main-silver', will be available in build *201401310001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)

Changeset: http://hg.netbeans.org/main-silver/rev/991972714aef
User: Maria Dalmatova <mromashova@netbeans.org>
Log: fixed bz#240915 - huge repository size (140Gb) during xRef checks
Introduced another maintenance mechanism:
1) during write to the DoubleFileStrorage if size of one of the files (active or passive)
is more than 512 Mb we will invoke defragment method
2) when defragment is invoked we will move data from passive to active file for one iteration (means we ignore maintenance interval)