Hardware vs. Software Sample Clauses

Hardware vs. Software. The results of the comparison of the hardware and software implementations are presented on the following Tables. In Table 8 the comparison of the software execution time with the hardware execution time with 1 MI calculation core is presented, while Table 9 presents the same comparison but with 2 cores running on the hardware. The experiments presented here and in the next section were done using 100.000 length time series for two random variables. The random variables represent stocks, while the time series are their values over time. The datasets were taken from the data provided by Spring. The software used in these experiments is the equivalent single thread implementation of the algorithm. It is written in C and the pdf estimation part is also used on the hardware implementation in the host code segment. As a first conclusion by the results it is clear that for small amounts of Bins the software implementation is much faster than the hardware. This happens because the hardware function call and the initialization of the streams need 5 - 30ms. On the other hand as the number of bins increases, the hardware performance increases, as the initialization time is a small fraction of the calculation time. The first architecture (1 MI calculation core) achieves a performance increase of up to 5.8x. For this implementation 3 of the 8 streams to the DFEs were used and only 5% of the available FPGA resources. Num of Bins SW(sec) HW1(sec) SpeedUp 100 0.002 0.031 0.06 500 0.025 0.036 0.69 1000 0.095 0.046 2 2000 0.4 0.1 4 5000 2.5 0.45 5.6 10000 10.3 1.8 5.7 20000 41.5 7.1 5.8 40000 159 30.5 5.3 Table 8:SW vs. HW MI calculation time with 1 core As mentioned above, there are 8 streams available for data streaming between the CPU and the DFE. In order to utilize more of the available bandwidth the pdfs were divided by two, which allows the use of 6 streams. Actually 5 streams are utilized as the pdf that was streamed R times is now streamed R/2 times instead. Also by using 2 processing cores the processing power of the hardware is doubled. This improvement allowed an increase on performance of up to 9.4x for large number of Bins. Equation (1) allows the parallelization of the algorithm. The maximum available bandwidth is the limiting factor as the 2 core implementation utilizes only 10% of the available FPGA resources while using 5 of the 8 available streams. Num of Bins SW(sec) HW2(sec) SpeedUp 100 0.002 0.036 0.05 500 0.025 0.037 0.68 1000 0.095 0.047 2 2000 0.4 ...
AutoNDA by SimpleDocs

Related to Hardware vs. Software

  • Embedded Software To the extent any goods contain Embedded Software (defined below) that is not Buyer’s Property, no title to such Embedded Software shall pass to Buyer, and Supplier shall grant Buyer, its customers and all other users a non-exclusive worldwide, irrevocable, perpetual, royalty-free right to use, load, install, execute, demonstrate, market, test, resell, sublicense and distribute such Embedded Software as an integral part of such goods or for servicing the goods (the “Buyer-Required License”). If such Embedded Software or any part thereof is owned by a third party, prior to delivery, Supplier shall obtain the Buyer-Required License from such third-party owner. “Embedded Software” means software necessary for operation of goods and embedded in and delivered as an integral part of goods.

  • Hardware and Software In order to use the Services, you must obtain and maintain, at your expense, compatible mobile hardware and software as specified by Credit Union from time to time. Credit Union is not responsible for any third party software you may need to use the Services. Any such software is accepted by you as is and is subject to the terms and conditions of the software agreement you enter into directly with the third party software provider at time of download and installation.

  • Server Software Subject to the terms and conditions of this XXXX, Vocera grants you the non-exclusive right to (i) install and run (“Use”) the Server Software on computer systems (each, a “Server Computer”) located at End User’s Facilities in the geographic territory designated above (“Territory”); (ii) to Use the Client Software in conjunction with Authorized Client Devices and such Server Computers; and (iii) for pilot licenses for certain Software provided on a trial basis, use such Software for the limited term specified by Vocera in writing. You may Use the standard Server Software on one primary Server Computer (or a primary cluster of computers suitably configured for productive use of the Server Software). You may install backup copies of the Server Software on backup Server Computers to provide redundancy in the event of failure of the primary Server Computer(s) but, unless you have acquired additional licenses or a failover license from Vocera, you may not run such backup or additional copies concurrently with the primary copies. Vocera grants you the right to use the applicable License Key issued by Vocera only to enable Use of the Server Software in conjunction with the licensed Server Computers. Server Software may be licensed for a Subscription Term as specified in the Quote.

  • Antivirus software All workstations, laptops and other systems that process and/or store PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY must have installed and actively use comprehensive anti-virus software solution with automatic updates scheduled at least daily.

  • Client Software You may only use the client software with the ERP solution. You may install an unlimited number of copies of the client software to access your ERP solution.

  • Licensed Software Computer program(s) provided by Contractor in connection with the Deliverables, subject to Section 14 of this Contract.

  • Required hardware and software The minimum system requirements for using the DocuSign system may change over time. The current system requirements are found here: xxxxx://xxxxxxx.xxxxxxxx.xxx/guides/signer-guide- signing-system-requirements. Acknowledging your access and consent to receive and sign documents electronically To confirm to us that you can access this information electronically, which will be similar to other electronic notices and disclosures that we will provide to you, please confirm that you have read this ERSD, and (i) that you are able to print on paper or electronically save this ERSD for your future reference and access; or (ii) that you are able to email this ERSD to an email address where you will be able to print on paper or save it for your future reference and access. Further, if you consent to receiving notices and disclosures exclusively in electronic format as described herein, then select the check-box next to ‘I agree to use electronic records and signatures’ before clicking ‘CONTINUE’ within the DocuSign system. By selecting the check-box next to ‘I agree to use electronic records and signatures’, you confirm that: • You can access and read this Electronic Record and Signature Disclosure; and • You can print on paper this Electronic Record and Signature Disclosure, or save or send this Electronic Record and Disclosure to a location where you can print it, for future reference and access; and

  • Third Party Software 1. The Software may contain third party software that requires and/or additional terms and conditions. Such required third party software notices and/or additional terms and conditions are located at xxxx://xxx.xxxxxxxxx.xxx/thirdparty/index.html and are made a part of and incorporated by reference into this XXXX. By accepting this XXXX, You are also accepting the additional terms and conditions, if any, set forth therein.

  • Software Use Case Red Hat Enterprise Virtualization Supported on physical hardware solely to support virtual quests. Red Hat Enterprise Virtualization is designed to run and manage virtual instances and does not support user-space applications. Red Hat Enterprise Virtualization may be used as a virtual desktop infrastructure solution, however, the Subscription does not come with any software or support for the desktop operating system. You must purchase the operating system for each instance of a desktop or server separately.

  • Software Title and ownership to Existing Software Product(s) delivered by Contractor under the Contract that is normally commercially distributed on a license basis by the Contractor or other independent software vendor proprietary owner (“Existing Licensed Product”), embedded in the Custom Products, shall remain with Contractor or the proprietary owner of other independent software vendor(s) (ISV). Effective upon acceptance, such Product shall be licensed to Authorized User in accordance with the Contractor or ISV owner’s standard license agreement, provided, however, that such standard license, must, at a minimum: (a) grant Authorized User a non-exclusive, perpetual license to use, execute, reproduce, display, perform, adapt (unless Contractor advises Authorized User as part of Contractor’s proposal that adaptation will violate existing agreements or statutes and Contractor demonstrates such to the Authorized User’s satisfaction) and distribute Existing Licensed Product to the Authorized User up to the license capacity stated in the Purchase Order or work order with all license rights necessary to fully effect the general business purpose(s) stated in the Bid or Authorized User’s Purchase Order or work order, including the financing assignment rights set forth in paragraph (c) below; and (b) recognize the State of New York as the licensee where the Authorized User is a state agency, department, board, commission, office or institution. Where these rights are not otherwise covered by the ISV’s owner’s standard license agreement, the Contractor shall be responsible for obtaining these rights at its sole cost and expense. The Authorized User shall reproduce all copyright notices and any other legend of ownership on any copies authorized under this clause. Open source software is developed independently of Contractor and may be governed by a separate license (“open source software”). If the open source software is governed by a separate License and provided under this Contract, Contractor shall provide a copy of that license in the applicable Documentation and the Authorized User's license rights and obligations with respect to that open source software shall be defined by those separate license terms and subject to the conditions, if any, therein. Nothing in this Contract shall restrict, limit, or otherwise affect any rights or obligations the Authorized User may have, or conditions to which the Authorized User may be subject, under such separate open source license terms.

Time is Money Join Law Insider Premium to draft better contracts faster.