Consolidating Java Stored Procedure JAR Files

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Complex Java Stored Procedures (JSPs) in database applications lead to performance issues due to multiple disk accesses and page faults, degrading the performance of both individual applications and the database as a whole, as they rely on multiple large JAR files for method execution.

Innovation Solution

A method to detect and pack JSP methods used by an application into a single new JAR file, replacing original JSP definitions to call methods from this packed file, reducing disk access and improving processing throughput by caching the packed JAR file in memory.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of repair

If multiple separate JAR files are used to organize JSP methods by functionality, then ease of support and serviceability is improved, but disk access frequency increases causing performance degradation

Engineering Contradiction:
ImproveserviceabilityVSAvoidprocessing throughput
Core Design Contradiction:
Ease of repairVSProductivity

Solution Approach 1:

The patent merges multiple separate JAR files containing JSP methods into a single consolidated JAR file. This consolidation reduces the number of disk accesses required during application execution, as all needed JSP methods are now located in one file rather than requiring access to multiple separate files. The merging maintains serviceability by preserving the organizational structure within the consolidated file while eliminating the performance penalty of multiple disk accesses.

Inventive Principle:
Principle #5Merging (Combining)

2Adaptability or versatility

If JAR files are kept separate and distributed, then adaptability to different applications is improved, but memory usage increases due to loading multiple large files

Engineering Contradiction:
Improveapplication compatibilityVSAvoidmemory usage
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent combines multiple JAR files into one consolidated JAR file that contains all necessary JSP methods. This single file approach reduces memory usage because the system only needs to load and manage one file in memory at a time, rather than maintaining multiple large JAR files simultaneously. The consolidated file maintains adaptability by including all necessary methods from the original separate files, allowing the same file to serve multiple applications.

Inventive Principle:
Principle #5Merging (Combining)

3Reliability

If multiple disk requests are made to access JSP methods from different JAR files, then method functionality is maintained, but access time increases due to disk page faults

Engineering Contradiction:
Improvemethod executionVSAvoidaccess time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent consolidates JSP methods from multiple JAR files into a single JAR file, which eliminates the need for multiple disk requests when executing methods. By having all methods in one file, the system can load the entire file into memory once and access any method without additional disk page faults, significantly reducing access time while maintaining reliable method execution.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent performs preliminary consolidation of all JSP methods into a single JAR file before execution. This preliminary action ensures that when the application runs, all necessary methods are already available in one location, eliminating the need for repeated disk accesses during method execution and reducing access time.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8352911B2Techniques for constructing and using run-time JAVA archives (JAR) for JAVA Stored Procedures (JSPS)
Publication Date: 2013.01.08 TERADATA US INC
  • US8352911B2 patent drawing
  • US8352911B2 patent drawing
  • US8352911B2 patent drawing

AI summary

Techniques for constructing and using run-time JAVA Archive (JAR) files for JAVA Stored Procedures (JSPs) are provided. JSP methods referenced by an application via a plurality of different JAR files are extracted and packed into a single packed JAR file. When the application tries to execute a JSP, the attempt to process the JSP methods is redirected to a new JSP that calls the single packed JAR file.