{'fraction_non_alphanumeric': 0.02318623784592371, 'fraction_numerical': 0.0, 'mean_word_length': 5.463768115942029, '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}}
Migrating a C-Based CAD Tool to an Object-Oriented Database/C++ environment: Conversion Costs and Performance Analysis

Abstract : This paper examines the potential of object-oriented databases to support complex design applications. To do this we migrated the Magic very large scale integrated (VLSI) circuit design tool written in the C language to a new environment in which Magic's existing file management code is replaced with a C++ language interface to the commercial object-oriented database management system (OODBMS) product Object Store. In our initial implementation we found the performance of this tool as implemented on the OODBMS to be marginally faster than the tool as currently implemented with a flat file system in several critical areas. Increased functionality, including version management, multi- user concurrency control, and recovery, are now possible with the converted system. However, we found the conversion process itself time consuming and fraught with software engineering perils; the final product is not significantly more or less maintainable. We conclude that the conversion of large, complex systems should not be undertaken without experienced programmers nor without a pressing need for increased database functionality. Conversion of such systems to improve performance alone should be avoided.