Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EmfIndex Comparison"
Line 8: | Line 8: | ||
= Performance = | = Performance = | ||
− | == Indexing | + | == Indexing == |
+ | |||
+ | === Indexing time === | ||
This test measured the time which is needed to index x-times the content of Ecore.ecore. (Containing 393 instances of EObject and 520 references) | This test measured the time which is needed to index x-times the content of Ecore.ecore. (Containing 393 instances of EObject and 520 references) | ||
Line 29: | Line 31: | ||
| 43,5 s | | 43,5 s | ||
|} | |} | ||
+ | |||
+ | [[Image:EmfIndex indexingTime.png]] | ||
+ | |||
+ | === Memory consumption === | ||
+ | |||
+ | This test measured the in memory size of the index. In the SAP case, paging was disabled | ||
+ | |||
+ | {| cellspacing="1" cellpadding="1" border="1" style="width: 376px; height: 130px;" | ||
+ | |- | ||
+ | | <br> | ||
+ | | 1000 | ||
+ | | 2000 | ||
+ | | 3000 | ||
+ | |- | ||
+ | | SAP | ||
+ | | 136 million bytes | ||
+ | | 278 million bytes | ||
+ | | 408 million bytes | ||
+ | |- | ||
+ | | Itemis | ||
+ | | 169 million bytes | ||
+ | | 340 million bytes | ||
+ | | 508 million bytes | ||
+ | |} | ||
+ | |||
+ | [[Image:EmfIndex_AllInMemory.png]]<br> | ||
+ | |||
+ | == Query response time == | ||
+ | |||
+ | === Query All EObject and all EReferences === | ||
+ | |||
+ | {| width="200" cellspacing="1" cellpadding="1" border="1" | ||
+ | |- | ||
+ | | <br> | ||
+ | | 1000 | ||
+ | | 2000 | ||
+ | | 3000 | ||
+ | |- | ||
+ | | SAP | ||
+ | | 0,3 s | ||
+ | | 0,45 s | ||
+ | | 0,65 s | ||
+ | |- | ||
+ | | Itemis | ||
+ | | 1,4 s | ||
+ | | 2,2 s | ||
+ | | 3,3 s | ||
+ | |} | ||
+ | |||
+ | [[Image:EmfIndex indexingTime.png]] | ||
+ | |||
+ | <br> |
Revision as of 03:53, 2 September 2009
This page is intended to compare the two index implementations form different viewpoints such as
- API
- Performance
- Memory Consumption
- How to build a convinient Query API on top of the low level API
Contents
Performance
Indexing
Indexing time
This test measured the time which is needed to index x-times the content of Ecore.ecore. (Containing 393 instances of EObject and 520 references)
|
1000 | 2000 | 3000 |
SAP | 15,4 s | 29,9 s | 45,3 s |
Itemis | 14,6 s | 28,4 s | 43,5 s |
Memory consumption
This test measured the in memory size of the index. In the SAP case, paging was disabled
|
1000 | 2000 | 3000 |
SAP | 136 million bytes | 278 million bytes | 408 million bytes |
Itemis | 169 million bytes | 340 million bytes | 508 million bytes |
Query response time
Query All EObject and all EReferences
|
1000 | 2000 | 3000 |
SAP | 0,3 s | 0,45 s | 0,65 s |
Itemis | 1,4 s | 2,2 s | 3,3 s |