Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 343155 - [Scalability] Java discoverer time benchmark
Summary: [Scalability] Java discoverer time benchmark
Status: NEW
Alias: None
Product: MoDisco
Classification: Modeling
Component: Technologies (show other bugs)
Version: 0.9.0   Edit
Hardware: PC Windows 7
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 355388
Blocks:
  Show dependency tree
 
Reported: 2011-04-18 09:17 EDT by Nicolas Bros CLA
Modified: 2011-09-29 12:41 EDT (History)
1 user (show)

See Also:
gdupe: juno+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolas Bros CLA 2011-04-18 09:17:54 EDT 
We have an existing Java benchmark (org.eclipse.gmt.modisco.java.discoverer.benchmark), but since it tries to measure both execution time and memory use, it regularly calls the GC before measuring instantaneous memory use, and so it ends up degrading performance severely.

So, we need a new Java discoverer benchmark that primarily measures execution time.
Comment 1 Gregoire Dupe CLA 2011-09-28 10:55:26 EDT 
This is planned by the bug Bug 355388.