Changes between Version 5 and Version 6 of MetaData
- Timestamp:
- 02/12/08 14:34:23 (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MetaData
v5 v6 55 55 }}} 56 56 57 == Profiling Results == 58 Including meta data with each packet increases the amount of overhead used in mashalling data objects as they are passed from one component to another. As described in the section above, no modifications to the component code are required, however the additional data not utilized by the port could slow the component down. 57 == Latency Results == 58 Including meta data with each packet increases the amount of overhead used in mashalling data objects as they are passed from one component to another. As described in the section above, no modifications to the component code are required, however the many parties have expressed concern that the additional data not utilized by the port could slow the component down. 59 60 Several tests were run to compare the amount of latency between components for different data types. Numerous papers discuss the topic of latency through CORBA, so we won't get into hairy details here. 59 61 60 62 The results for profiling latency vs. packet size can be seen below. Results were averaged over 100,000 trials. Trends were consistent across different platforms. … … 70 72 The exact interfaces used for analysis can be found in a [source:/customInterfaces/branches/custom-testable-interface branch] of custom interfaces. 71 73 72 These results suggest that adding basic metadata with each packet adds negligible overhead in terms of latency. 74 These results suggest that adding basic metadata with each packet adds negligible overhead in terms of latency. Keep in mind that extracting the metadata object tags was not incorporated into the test (e.g. the amount of time it would take to parse an XML object). 75 76 Questions and concerns should be directed to JosephGaeddert 73 77 74 78 == Software Status ==
