Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 343155

Summary:	[Scalability] Java discoverer time benchmark
Product:	[Modeling] MoDisco	Reporter:	Nicolas Bros <nicolas.bros>
Component:	Technologies	Assignee:	Project Inbox <modisco.web-inbox>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P5	CC:	gdupe
Version:	0.9.0	Flags:	gdupe: juno+
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:
Bug Depends on:	355388
Bug Blocks:

Description Nicolas Bros

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

2011-09-28 10:55:26 EDT

This is planned by the bug Bug 355388.