Bug 560250 - [functional debug expr] Cache compiled code for similar contexts
Summary: [functional debug expr] Cache compiled code for similar contexts
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.15   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks: 560247
  Show dependency tree
 
Reported: 2020-02-17 20:58 EST by Jesper Moller CLA
Modified: 2024-02-12 13:11 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jesper Moller CLA 2020-02-17 20:58:31 EST
The current code is inefficient, especially when evaluating expressions in the expressions view, due to the current evaluation process:
1. Compile expr to AST
2. Visit AST and generate instructions for evaluation
3. For functional expressions:
3.1 Generate snippet from AST
3.2 Compule snippet to bytecode
3.3 Load snippet classes
3.4 Instantiate snippet
3.5 Run snippet

Some LRU caching at level 2 could improve this dramatically.
Comment 1 Eclipse Genie CLA 2022-02-21 12:42:07 EST
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.

--
The automated Eclipse Genie.
Comment 2 Eclipse Genie CLA 2024-02-12 13:11:31 EST
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.

--
The automated Eclipse Genie.