BSP PERFORMANCE AND TESTING Sample Clauses

BSP PERFORMANCE AND TESTING. 7.2.1 Flat compilation flow There are two compilation flows for OpenCL designs. The first is the regular flow where the IP components such as memories, PCIe and IO connections are locked down in a fixed location. This guarantees that the OpenCL designs will work regardless of how low the compiled kernel clock frequency is. This ensures the critical components such as the PCIe and DDR memories always meet timing. For a flat flow, no components are locked down and therefore there is no guarantee that the critical components always meet timing. A flat flow has advantages in that extra functionality can be added to the BSP without a major rework to the BSP floor planning. Given that the OPERA BSP is to be continuously improved over the course of the project a flat flow will be used for initial OpenCL design and MICMAC port. Compilation of existing software using a flat flow have proven that critical components of the design still meet timing with a flat flow, if the PCIe is de-rated to Gen2. De-rating of the PCIe to Gen2 has no significant impact (see 7.2.4). Figure 17: Example flat build showing the base IP (PCIe, etc) in red (Arria 10 660-SOC) With the flat flow, there is no base region and the Altera tools can place the kernel logic amongst the board logic. So, whilst not all logic can be used, there are no floor planned regions where the kernel logic cannot be placed. This leads to a lower board resource usage than for a fixed floor planned BSP. The resource of the flat BSP is given below. ALMS FFs DSPs RAMs 23483 (9.33%) 93932 (9.33%) 231 (10.84%) Table 10 : FPGA prototype BSP resource use 7.2.2 Serial link Loopback A QSFP serial channels loopback OpenCL test design was used to prove the serial channels work (See 0). Here a special loopback cable connects one QSFP port to the other. The loopback tests bursts of different sizes transferred over both serial links. The following table illustrates the bandwidth measured for different packet sizes and which includes the setup time require by the OpenCL API. 3 Bandwidth Gbytes/Sec 0 1000 10000 100000 1000000 10000000 100000000 1E+09 Figure 18 : Serial link bandwidth for various burst sizes (Bytes) running in OpenCL. The maximum theoretical bandwidth of the serial links is 5 GBytes/Sec for each 40 Gbit link.
Sample 1
AutoNDA by SimpleDocs

Related to BSP PERFORMANCE AND TESTING

  • CONTRACTOR PERFORMANCE AUDIT The Contractor shall allow the Authorized User to assess Contractor’s performance by providing any materials requested in the Authorized User Agreement (e.g., page load times, response times, uptime, and fail over time). The Authorized User may perform this Contractor performance audit with a third party at its discretion, at the Authorized User’s expense. The Contractor shall perform an independent audit of its Data Centers, at least annually, at Contractor expense. The Contractor will provide a data owner facing audit report upon request by the Authorized User. The Contractor shall identify any confidential, trade secret, or proprietary information in accordance with Appendix B, Section 9(a), Confidential/Trade Secret Materials.

  • Performance Testing 7.2.1 The Design-Builder shall direct and supervise the tests and, if necessary, the retests of the Plant using Design-Builder’s supervisory personnel and the Air Emissions Tester shall conduct the air emissions test, in each case, in accordance with the testing procedures set forth in Exhibit A (the “Performance Tests”), to demonstrate, at a minimum, compliance with the Performance Guarantee Criteria. Owner is responsible for obtaining Air Emissions Tester and for ensuring Air Emissions Tester’s timely performance. Design-Builder shall cooperate with the Air Emissions Tester to facilitate performance of all air emissions tests. Design-Builder shall not be held responsible for the actions of Owner’s employees and third parties involved in the Performance Testing, including but not limited to Air Emissions Tester. 7.2.2 No later than thirty (30) Days prior to the earlier of the Scheduled Substantial Completion Date or Substantial Completion, Design-Builder shall provide to Owner for review a detailed testing plan for the Performance Tests (other than for air emissions). Owner and Design-Builder shall agree upon a testing plan that shall be consistent with the Performance Test Protocol contained in Exhibit A hereto. After such agreement has been reached, Design-Builder shall notify the Owner five (5) business days prior to the date Design-Builder intends to commence the Performance Tests and shall notify the Owner upon commencement of the Performance Tests. Owner and Independent Engineer each have the right to witness all testing, including the Performance Tests and any equipment testing, whether at the Site or at the Subcontractor’s or equipment supplier’s premises during the course of this Agreement. Notwithstanding the foregoing sentence, Owner shall bear the costs of providing a witness to any such testing and all such witnesses shall comply at all times with Design-Builder’s, Subcontractor’s or equipment supplier’s safety and security procedures and other reasonable requirements, and otherwise conduct themselves in a manner that does not interfere with Design-Builder’s, Subcontractor’s or equipment supplier’s activities or operations. 7.2.3 Design-Builder shall provide to Owner a Performance Test report (excluding results from air emissions testing), including all applicable test data, calculations and certificates indicating the results of the Performance Tests and, within five (5) business days of Owner’s receipt of such results, Owner, Independent Engineer and Design-Builder will jointly inspect such Work and review the results of the Performance Tests to verify that the Performance Guarantee Criteria have been met. If Owner or Independent Engineer reasonably determines that the Performance Guarantee Criteria have not been met, Owner shall notify Design-Builder the reasons why Owner determined that the Performance Guarantee Criteria have not been met and Design-Builder shall promptly take such action or perform such additional work as will achieve the Performance Guarantee Criteria and shall issue to the Owner another notice in accordance with Section 7.2.2; provided however that if the notice relates to a retest, the notice may be provided no less than two (2) business days prior to the Performance Tests. Such procedure shall be repeated as necessary until Owner and Independent Engineer verifies that the Performance Guarantee Criteria have been met. 7.2.4 If Owner, for whatever reason, prevents Design-Builder from demonstrating the Performance Guarantee Criteria within thirty (30) Days of Design-Builder’s notice that the Plant is ready for Performance Testing, then Design-Builder shall be excused from demonstrating compliance with the Performance Guarantee Criteria during such period of time that Design-Builder is prevented from demonstrating compliance with the Performance Guarantee Criteria; provided however that Design-Builder will be deemed to have fulfilled all of its obligations to demonstrate that the Plant meets the Performance Guarantee Criteria should such period of time during which Design-Builder is prevented from demonstrating the Performance Criteria exceed thirty (30) Days or extend beyond the Final Completion Date.

  • Ongoing Performance Measures The Department intends to use performance-reporting tools in order to measure the performance of Contractor(s). These tools will include the Contractor Performance Survey (Exhibit H), to be completed by Customers on a quarterly basis. Such measures will allow the Department to better track Vendor performance through the term of the Contract(s) and ensure that Contractor(s) consistently provide quality services to the State and its Customers. The Department reserves the right to modify the Contractor Performance Survey document and introduce additional performance-reporting tools as they are developed, including online tools (e.g. tools within MFMP or on the Department's website).

  • Covenants of Performance Measurement No interference. Registry Operator shall not interfere with measurement Probes, including any form of preferential treatment of the requests for the monitored services. Registry Operator shall respond to the measurement tests described in this Specification as it would to any other request from an Internet user (for DNS and RDDS) or registrar (for EPP). ICANN testing registrar. Registry Operator agrees that ICANN will have a testing registrar used for purposes of measuring the SLRs described above. Registry Operator agrees to not provide any differentiated treatment for the testing registrar other than no billing of the transactions. ICANN shall not use the registrar for registering domain names (or other registry objects) for itself or others, except for the purposes of verifying contractual compliance with the conditions described in this Agreement. PUBLIC INTEREST COMMITMENTS Registry Operator will use only ICANN accredited registrars that are party to the Registrar Accreditation Agreement approved by the ICANN Board of Directors on 27 June 2013 in registering domain names. A list of such registrars shall be maintained by ICANN on ICANN’s website. (Intentionally omitted. Registry Operator has not included commitments, statements of intent or business plans provided for in its application to ICANN for the TLD.) Registry Operator agrees to perform the following specific public interest commitments, which commitments shall be enforceable by ICANN and through the Public Interest Commitment Dispute Resolution Process established by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/picdrp), which may be revised in immaterial respects by ICANN from time to time (the “PICDRP”). Registry Operator shall comply with the PICDRP. Registry Operator agrees to implement and adhere to any remedies ICANN imposes (which may include any reasonable remedy, including for the avoidance of doubt, the termination of the Registry Agreement pursuant to Section 4.3(e) of the Agreement) following a determination by any PICDRP panel and to be bound by any such determination. Registry Operator will include a provision in its Registry-Registrar Agreement that requires Registrars to include in their Registration Agreements a provision prohibiting Registered Name Holders from distributing malware, abusively operating botnets, phishing, piracy, trademark or copyright infringement, fraudulent or deceptive practices, counterfeiting or otherwise engaging in activity contrary to applicable law, and providing (consistent with applicable law and any related procedures) consequences for such activities including suspension of the domain name. Registry Operator will periodically conduct a technical analysis to assess whether domains in the TLD are being used to perpetrate security threats, such as pharming, phishing, malware, and botnets. Registry Operator will maintain statistical reports on the number of security threats identified and the actions taken as a result of the periodic security checks. Registry Operator will maintain these reports for the term of the Agreement unless a shorter period is required by law or approved by ICANN, and will provide them to ICANN upon request. Registry Operator will operate the TLD in a transparent manner consistent with general principles of openness and non-discrimination by establishing, publishing and adhering to clear registration policies.

  • Annual Performance Evaluation On either a fiscal year or calendar year basis, (consistently applied from year to year), the Bank shall conduct an annual evaluation of Executive’s performance. The annual performance evaluation proceedings shall be included in the minutes of the Board meeting that next follows such annual performance review.

  • KEY PERFORMANCE INDICATORS 10.1 The Supplier shall at all times during the Framework Period comply with the Key Performance Indicators and achieve the KPI Targets set out in Part B of Framework Schedule 2 (Goods and/or Services and Key Performance Indicators).

  • Performance Tests Contractor shall perform Performance Tests in accordance with Section 11.2 of the Agreement and Attachment S.

  • Annual Performance Review The Employee’s performance of his duties under this Agreement shall be reviewed by the Board of Directors or a committee of the Board of Directors at least annually and finalized within thirty (30) days of the receipt of the annual audited financial statements. The Board of Directors or a committee of the Board of Directors shall additionally review the base salary, bonus and benefits provided to the Employee under this Agreement and may, in their discretion, adjust the same, as outlined in Addendum B of this Agreement, provided, however, that Employee’s annual base salary shall not be less than the base salary set forth in Section 4(A) hereof.

  • The Performance Improvement Process (a) The Performance Improvement Process will focus on the risks of non- performance and problem-solving. It may include one or more of the following actions: (1) a requirement that the HSP develop and implement an improvement plan that is acceptable to the LHIN; (2) the conduct of a Review; (3) a revision and amendment of the HSP’s obligations; and (4) an in-year, or year end, adjustment to the Funding, among other possible means of responding to the Performance Factor or improving performance. (b) Any performance improvement process begun under a prior service accountability agreement that was not completed under the prior agreement will continue under this Agreement. Any performance improvement required by a LHIN under a prior service accountability agreement will be deemed to be a requirement of this Agreement until fulfilled or waived by the LHIN.

  • Performance Excused The Affected Party, to the extent rendered unable to perform its obligations or part thereof under this Agreement as a consequence of the Force Majeure Event shall be excused from performance of the obligations. Provided that, the excuse from performance shall be of no greater scope and of no longer duration than is reasonably warranted by the Force Majeure Event. Provided further, nothing contained herein shall absolve the Affected Party from any payment obligations accrued prior to the occurrence of the underlying Force Majeure Event.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!