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 31359 - Improve storing of monitor records
Summary: Improve storing of monitor records
Status: VERIFIED FIXED
Alias: None
Product: javaee
Classification: Unclassified
Component: HTTP Monitor (show other bugs)
Version: 3.x
Hardware: All All
: P3 blocker (vote)
Assignee: Ana.von Klopp
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2003-02-22 02:18 UTC by Ana.von Klopp
Modified: 2006-01-20 13:27 UTC (History)
0 users

See Also:
Issue Type: TASK
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ana.von Klopp 2003-02-22 02:18:45 UTC
The monitor records are parsed and kept in memory as they 
are sent to the IDE. I can make some improvements to how 
this is done to reduce memory consumptions.
Comment 1 Ana.von Klopp 2003-02-22 02:20:39 UTC
The nodes get added to the tree representation used by the 
GUI whether the window is open or not. Should check whether 
the window is showing before doing this. They get parsed 
anyway when the window is opened. 




Note to QA: the fix to this will have to be verified by 
dev.
Comment 2 Ana.von Klopp 2003-02-25 23:53:14 UTC
Turned out this was less of a problem than I thought. 




I modified the servlet which receives the transactions in 
such a way that unless the GUI is opened, the data records 
are not parsed for the purposes of adding a node, they're 
just saved to disk.The client reads the records when it 
opens anyway. In case the window is opened, they are parsed 
and the transactions are added immediately. 




I was concerned that when the records are parsed, they're 
automatically stored in memory, but this only happens when 
the user actually inspects the record (in which case 
they're likely to look at it more than once). So the list 
of records in memory won't grow larger than the ones the 
user actually looks at. Users who actively use the monitor 
need to purge the list of current transactions fairly 
regularly, so this should not grow very large even if the 
IDE is used over a period of time.  




Comment 3 Lukasz Grela 2006-01-20 13:27:34 UTC
v.