{'fraction_non_alphanumeric': 0.017379679144385027, 'fraction_numerical': 0.0053475935828877, 'mean_word_length': 5.241666666666666, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
THE COMPILE-AND RUN-TIME PERFORMANCE CONSIDERATIONS OF IMPLEMENTING CROSS-CUTTING CONCERNS AS ASPECTS

Aspects are frequently cited as an ideal solution to large cross-cutting concerns such as logging and first failure data capture. The flexibility of the AspectJTM language with its use of wildcards combined with a powerful runtime reflection API allows the creation of simple and extensible aspects. The paper outlines the performance implications of weaving aspects with existing programs and the relative run-time performance of woven programs in terms of throughput and scalability. This paper is an extension to our previous work [Dalton et al, 2003]; the focus is on the new developments in AspectJ technology and deeper empirical analysis.