{'fraction_non_alphanumeric': 0.014705882352941176, 'fraction_numerical': 0.0, 'mean_word_length': 5.948979591836735, '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}}
Comparison of Triplestore Architectures in the Oracle RDBMS

Several different database configurations for supporting triplestores are implemented in Oracle and compared to each other in terms of execution speed across several queries. The configurations considered are a simple baseline architecture, a Triple-Triple architecture composed of redundant copies of the triples table with different indexing orders, and a configuration based on bitmap join indexes, which are exclusive to the Oracle RDBMS. Sadly, the results for the alternate architectures show no significant improvement over the baseline architecture, seemingly due to inexplicable behavior of Oracle’s internals.