Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 344791 - Memory (Client and Server): CodeCache uses a lot of memory
Summary: Memory (Client and Server): CodeCache uses a lot of memory
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Scout (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-05 03:45 EDT by Matthias Zimmermann CLA
Modified: 2021-08-19 10:58 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matthias Zimmermann CLA 2011-05-05 03:45:13 EDT
For systems with a large number of codes, the size of the code cache is a problem.

1) AbstractCode contains per default a HashMap and ArrayList for child codes. Most codes however do not contain any children at all. -> should be created on demand.

2) The class CodeRow contains many attributes, which are not always used (initialized with null, pointer still uses memory). To avoid this AbstractCode and MutableCode should not be initialized with CodeRow, but with an interface, such that a custom implementation could be used.

3) Sometimes CodeRows need to be converted to LookupRows (e.g. CodeLookupCall). The conversion is time consuming (or memory consuming if cached). CodeRow looks almost the same as LookupRow, but contains some more values. -> an interface for LookupRow and the same base class would save the problem.

Problems are solved for project Sika, but fix should be included in Scout, for other projects.
Comment 1 Matthias Zimmermann CLA 2011-05-05 03:46:18 EDT
fixed on 17.1.2011, #95492
Comment 2 Matthias Zimmermann CLA 2011-06-28 08:27:15 EDT
shipped with eclipse scout 3.7.0