Ticket #41 (closed task: fixed)
Improve LIFO and Vector Coordinator performance
| Reported by: | T.Doenz | Owned by: | T.Doenz |
|---|---|---|---|
| Priority: | minor | Milestone: | 2.1 |
| Component: | CAPI3-Native | Version: | 2.0 |
| Keywords: | Cc: |
Description
The LIFO and Vector coordinators are currently very slow (especially for take operations), compared to similar coordinators (FIFO, Key) and the old MozartSpaces version. The reason lies probably in the coordinator implementations, which should be tested, reviewed and improved. See the first benchmark results (100826_space_perftest.ppt) for detailed numbers.
Change History
comment:1 Changed 18 months ago by T.Doenz
- Owner changed from M.Barisits to T.Doenz
- Status changed from new to assigned
- Milestone set to 2.1
comment:2 Changed 16 months ago by T.Doenz
The LIFO performance has been improved with SVN rev. 10101. The Vector performance has been improved with SVN rev. 10104, but it is still slow. The main reason/line for its inferior performance needs further changes and is marked with a TODO comment
comment:4 Changed 6 months ago by T.Doenz
Due to the refactoring in SVN rev. 10957 also the Vector coordinator should now be faster, but benchmarks need to be performed to confirm that.
comment:5 Changed 6 months ago by T.Doenz
The changes in SVN rev. 10957 introduced a bug (the entry indices change when an entry at the beginning or in the middle is removed). The current version should be correct but has the same performance limitations as before.
comment:6 Changed 4 months ago by T.Doenz
- Status changed from assigned to closed
- Resolution set to fixed
I close the ticket because the current coordinator performance is acceptable. The performance of LIFO is comparable to FIFO. The performance of Vector is lower but not easy to improve because of the coordinator requirements (direct access with index).
