{'fraction_non_alphanumeric': 0.018518518518518517, 'fraction_numerical': 0.0, 'mean_word_length': 5.329787234042553, '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}}
HELP DEVELOPERS (FINALLY) FIND THEIR OWN PERFORMANCE DEFECTS

How early in the software development cycle are most performance defects found? Before or after QA? Industry pundits have long sought to reduce costs by fixing software defects earlier in the cycle. The path to these cost reductions, however, is fraught with road blocks. This paper focuses on a concrete testing regimen that works around these longstanding obstacles. It empowers developers to finally help locate their own performance defects, instead of relying solely on the assistance of specialized performance tuning experts.