Project

General

Profile

Actions

Feature #4501

closed

Identify fields in CDir which aren't permanently necessary

Added by Greg Farnum about 11 years ago. Updated about 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Performance/Resource Usage
Target version:
-
% Done:

0%

Source:
Development
Tags:
Backport:
Reviewed:
Affected Versions:
Component(FS):
MDS
Labels (FS):
Pull request ID:

Description

The CDir has some machinery for handling things like dirty data that isn't always necessary. Audit it for these members, group them logically, and sort the groups by memory size. Create tasks for moving each group into separately-allocated structs which can be moved in and out of memory on-demand. Each of these structs should probably be allocated using a boost::pool.

Actions

Also available in: Atom PDF