{'fraction_non_alphanumeric': 0.022243713733075435, 'fraction_numerical': 0.0, 'mean_word_length': 5.310975609756097, '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': 1, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Method based technique of compilation with compilation server

Compiler optimizations are difficult to implement and add complexity to a compiler. For this reason, compiler writers are selective about implementing them: they implement only the ones that they believe will be beneficial. Compilation Server (CS) is a server-assist mechanism to eliminate or reduce the compilation overhead. CS can compile and optimize code on behalf of clients.
 Broadly speaking, there are three interleaved steps in running java programs in a compiled environment: downloading the bytecodes, compiling and possibly optimizing the bytecodes, and running the compiled code. Optimized code typically runs faster than non-optimized code. We consider the possibility of moving compilation to a server. We demonstrate that there is a significant benefit to moving compilation to a server (i) lower execution time by reducing the overhead of optimization; (ii) lower memory management load on the client by reducing the footprint of the optimizing compiler.