To have a direct comparison between the onsite options of having Windows or Linux-based FPGA compile workers, NI used identical hardware and Xilinx compile tools as defined below. Since the LabVIEW FPGA Compile Cloud Service executes on one of a large set of potential server resources in the cloud NI cannot establish a one-to-one direct comparison. Instead, the equivalency definition below helps us to conservatively estimate the hardware resource allocation used for the compile benchmark.
Software installed on all workers is the Xilinx ISE 13.4 compilation tools which are shipped with the LabVIEW 2012 FPGA module.
FPGA Compile Worker Machine Specification
3.2GHz Intel Xeon W3565
12 GB of RAM
250GB HDD 7200rpm
One machine with 64-bit Windows 7
One machine with 64-bit RedHat Enterprise Linux 5.6
LabVIEW FPGA Cloud Compile Service Specification
Amazon Web Services High-Memory Extra Large Instance
6.5 EC2 Compute Units (2 virtual cores with 3.25 EC2 Compute Units each) equivalent to approximately 3.25 – 3.9 GHz 2007 Xeon processor**
17.1 GB of RAM
420 GB of instance storage
**The Xilinx compile tools only can leverage one processor core per compile job and therefore the compile service only utilizes 3.25 EC2 Compute Units. According to Amazon “One EC2 Compute Unit provides the equivalent CPU capacity of a 1.0-1.2 GHz 2007 Opteron or 2007 Xeon processor” and therefore the instance has processing resources equivalent to a 3.25 – 3.9 GHz 2007 Xeon processor.