Community
Participate
Working Groups
Performance/memory improvements for the native Common Base Event implementation. Based on discussions with an internal IBM group on using native Common Base Event implementation on constrained devices (e.g. Palm, PocketPC, etc.), the code should be thoroughly reviewed for possible performance/memory improvements.
For example, all setters persist the old value before setting the new value for no reason. For instance, char* oldLocalInstanceId = commonBaseEvent->_localInstanceId;
Part of this defect should include a thorough review of the native Common Base Event implementation with special focus on event de/serialization, factory and content handling (e.g. deep/shallow copy).
This work should extend to both Java (EMF and non-EMF) Common Base Event implementations. As such, changing summary accordingly.
P2 Highly desirable and planned for this release, but not stop ship normal A problem making a function difficult to use but no special work around is required
One potential performance improvement (analysis required) is to store the template Common Base Event as an XML fragment/document in the org.eclipse.hyades.logging.events.cbe.impl.TemplateContentHandlerImpl. When the completeEvent(CommonBaseEvent) method is invoked, the Common Base Event XML fragment/document would be de-serialized into the parameter Common Base Event. However, the org.eclipse.hyades.logging.events.cbe.util.SAXEventHandler would need to be changed to allow callers to provide a parameter Common Base Event and the SAXEventHandler would need to respect the existing properties in the parameter Common Base Event.
Sizing (PW): Design: 1 Code: 2 Test: 2 Documentation: 0.5 ------------------ Total: 5.5
Created attachment 30157 [details] EventHelpersPerformancePatch.txt
This defect should be a duplicate of 112371.
*** This bug has been marked as a duplicate of 112371 *** *** This bug has been marked as a duplicate of 112371 ***
Closing.
