Content Server Performance Certification via HTTP Load Testing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
There is a need to certify the performance of HTTP content servers to ensure they can handle varying demands of storing and archiving business documents efficiently, as performance issues can impact business software functionality and compliance with legal and regulatory standards.
Innovation Solution
A method and apparatus for certifying a content server performance using a content server interface, involving a test program that requests and records times for writing and retrieving documents, and determines certification based on predetermined thresholds, ensuring the server meets performance criteria.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a content server handles high volume of documents with varying sizes, then the server's storage capacity and flexibility are improved, but the performance certification becomes more complex and time-consuming
Solution Approach 1:
The patent applies parameter changes by systematically varying document size parameters (small, medium, large documents) and volume parameters (number of documents) in the certification process. The test program modifies these parameters to create different test scenarios, allowing comprehensive performance evaluation without requiring complex manual test design for each scenario.
Solution Approach 2:
The patent implements universality through a single test program that handles multiple document types and sizes using the same HTTP interface. The certification system universally applies the same testing methodology across varying document parameters, eliminating the need for separate certification processes for different document scenarios.
2Adaptability or versatility
If the content server stores both small and very large documents, then the storage versatility is improved, but the retrieval time and performance measurement become more variable and difficult to certify
Solution Approach 1:
The patent applies partial action by retrieving only the necessary portions of documents for testing purposes rather than requiring complete document transfers. The test program selectively tests retrieval performance with different document sizes without needing to fully process every document, reducing the time variability in performance measurement.
Solution Approach 2:
The patent implements preliminary action by pre-configuring the test program with knowledge of document locations, sizes, and types before retrieval begins. The system prepares test parameters and expectations in advance, allowing for more consistent and predictable retrieval time measurements across varying document sizes.
3Adaptability or versatility
If multiple vendors provide business software and content servers, then the system's adaptability and choice are improved, but ensuring consistent performance certification across different vendor implementations becomes more difficult
Solution Approach 1:
The patent implements universality by creating a vendor-agnostic test program that interfaces with content servers through standard HTTP protocols. The same certification methodology works across different vendor implementations, ensuring consistent performance measurement without requiring vendor-specific test procedures.
Solution Approach 2:
The patent applies feedback by having the test program receive and analyze performance data from the content server, then compare results against expected thresholds. This feedback mechanism ensures that performance certification is consistent across vendors by objectively measuring actual performance against standardized criteria.
Data Source
AI summary
Methods and apparatus, including computer program products, for certifying a performance of a content server using a content server interface. The method includes requesting, by a test program, an address of the content server and a security key from the content server interface; receiving the address and the security key from the content server interface; writing one or more documents to the address using hyper text transfer protocol (HTTP); recording a first amount of time for the writing; requesting a retrieval of data from the content server using HTTP; receiving the data from the content server; recording a second amount of time for the receiving; and certifying the content server if the first and second amounts of time are less than predetermined thresholds.