Random stress test. A set of random access experiments, called a four-corners test, evaluates performance of ** conditions, such as ** or ** , with either ** operations, or ** writes.
Random stress test Sample Clauses
Related to Random stress test
Acceptance Testing The MCP must have the capability to report all elements in the Minimum Data Set as set forth in the ODJFS Encounter Data Specifications and must submit a test file in the ODJFS-specified medium in the required formats prior to contracting or prior to an information systems replacement or update. Acceptance testing of encounter data is required as specified in Section 29(a)(v) of this Appendix.
Stability Testing Patheon may be requested to conduct stability testing on the Products in accordance with the protocols set out in the Specifications for the separate fees and during the time periods set out in Schedule C to a Product Agreement. Patheon will not make any changes to these testing protocols without prior written approval from Client. If a confirmed stability test failure occurs, Patheon will notify Client within one Business Day, after which Patheon and Client will jointly determine the proceedings and methods to be undertaken to investigate the cause of the failure, including which party will bear the cost of the investigation. Patheon will not be liable for these costs unless it has failed to perform the Manufacturing Services in accordance with the Specifications, cGMPs, and Applicable Laws. Patheon will give Client ail stability test data and results at Client’s request.
Performance Tests Contractor shall perform Performance Tests in accordance with Section 11.2 of the Agreement and Attachment S.
Product Testing Upon request, Customer shall provide Operator a laboratory report for each Product delivery by Customer or Customer’s supplier. Operator will not be obligated to receive Contaminated Product for throughput through the Pipelines, nor will Operator be obligated to accept Product that fails to meet the applicable quality specifications for the Berths under the BAUTA and any Terminal Service Orders issued thereunder.
Root Cause Analysis Upon Vendor's failure to provide the Services in accordance with the applicable Service Levels (for any reason other than a Force Majeure Event) Vendor will promptly (a) perform a root-cause analysis to identify the cause of such failure, (b) provide Prudential with a report detailing the cause of, and procedure for correcting, such failure, (c) obtain Prudential's written approval of the proposed procedure for correcting such failure, (d) correct such failure in accordance with the approved procedure, (e) provide weekly (or more frequent, if appropriate) reports on the status of the correction efforts, and (f) provide Prudential with assurances satisfactory to Prudential that such failure has been corrected and will not recur.
Asset Review Process Limitations The Asset Representations Reviewer will have no obligation:
Testing Landlord shall have the right to conduct annual tests of the Premises to determine whether any contamination of the Premises or the Project has occurred as a result of Tenant’s use. Tenant shall be required to pay the cost of such annual test of the Premises; provided, however, that if Tenant conducts its own tests of the Premises using third party contractors and test procedures acceptable to Landlord which tests are certified to Landlord, Landlord shall accept such tests in lieu of the annual tests to be paid for by Tenant. In addition, at any time, and from time to time, prior to the expiration or earlier termination of the Term, Landlord shall have the right to conduct appropriate tests of the Premises and the Project to determine if contamination has occurred as a result of Tenant’s use of the Premises. In connection with such testing, upon the request of Landlord, Tenant shall deliver to Landlord or its consultant such non-proprietary information concerning the use of Hazardous Materials in or about the Premises by Tenant or any Tenant Party. If contamination has occurred for which Tenant is liable under this Section 30, Tenant shall pay all costs to conduct such tests. If no such contamination is found, Landlord shall pay the costs of such tests (which shall not constitute an Operating Expense). Landlord shall provide Tenant with a copy of all third party, non-confidential reports and tests of the Premises made by or on behalf of Landlord during the Term without representation or warranty and subject to a confidentiality agreement. Tenant shall, at its sole cost and expense, promptly and satisfactorily remediate any environmental conditions identified by such testing in accordance with all Environmental Requirements. Landlord’s receipt of or satisfaction with any environmental assessment in no way waives any rights which Landlord may have against Tenant.
Financial testing The financial covenants set out in Clause 20.2 (Financial condition) shall be tested by reference to each of the financial statements and/or each Compliance Certificate delivered pursuant to Clause 19.2 (Compliance Certificate).
Access Control Landlord shall be the sole determinant of the type and amount of any access control or courtesy guard services to be provided to the Project, if any. IN ALL EVENTS, LANDLORD SHALL NOT BE LIABLE TO TENANT, AND TENANT HEREBY WAIVES ANY CLAIM AGAINST LANDLORD, FOR (I) ANY UNAUTHORIZED OR CRIMINAL ENTRY OF THIRD PARTIES INTO THE PREMISES, THE BUILDING OR THE PROJECT, (II) ANY DAMAGE TO PERSONS, OR (III) ANY LOSS OF PROPERTY IN AND ABOUT THE PREMISES, THE BUILDING OR THE PROJECT, BY OR FROM ANY UNAUTHORIZED OR CRIMINAL ACTS OF THIRD PARTIES, REGARDLESS OF ANY ACTION, INACTION, FAILURE, BREAKDOWN, MALFUNCTION AND/OR INSUFFICIENCY OF THE ACCESS CONTROL OR COURTESY GUARD SERVICES PROVIDED BY LANDLORD, IF ANY. Tenant shall provide such supplemental security services and shall install within the Premises such supplemental security equipment, systems and procedures as may reasonably be required for the protection of its employees and invitees, provided that Tenant shall coordinate such services and equipment with any security provided by Landlord. The determination of the extent to which such supplemental security equipment, systems and procedures are reasonably required shall be made in the sole judgment, and shall be the sole responsibility, of Tenant. Tenant acknowledges that it has neither received nor relied upon any representation or warranty made by or on behalf of Landlord with respect to the safety or security of the Premises or the Project or any part thereof or the extent or effectiveness of any security measures or procedures now or hereafter provided by Landlord, and further acknowledges that Tenant has made its own independent determinations with respect to all such matters.
Network Access Control The VISION Web Site and the Distribution Support Services Web Site (the “DST Web Sites”) are protected through multiple levels of network controls. The first defense is a border router which exists at the boundary between the DST Web Sites and the Internet Service Provider. The border router provides basic protections including anti-spoofing controls. Next is a highly available pair of stateful firewalls that allow only HTTPS traffic destined to the DST Web Sites. The third network control is a highly available pair of load balancers that terminate the HTTPS connections and then forward the traffic on to one of several available web servers. In addition, a second highly available pair of stateful firewalls enforce network controls between the web servers and any back-end application servers. No Internet traffic is allowed directly to the back-end application servers. The DST Web Sites equipment is located and administered at DST’s Winchester data center. Changes to the systems residing on this computer are submitted through the DST change control process. All services and functions within the DST Web Sites are deactivated with the exception of services and functions which support the transfer of files. All ports on the DST Web Sites are disabled, except those ports required to transfer files. All “listeners,” other than listeners required for inbound connections from the load balancers, are deactivated. Directory structures are “hidden” from the user. Services which provide directory information are also deactivated.
