1E Companion Products
Tachyon Server installer properties
Tachyon Agent installer and configuration properties
Tachyon Agent command-line parameters
Devices dashboard filters and charts
Responses Summary tab information
Tachyon Explorer comparison operators
Switch Command Lines
Tachyon Log Files
Tachyon release information
- Supported Platforms
|500 seats to 50,000 seats||500 seats to 250,000 seats|
Single Server Config
Split Server Config
Tachyon Switch Server Sizing
- The recommended configuration for the Tachyon Switch when hosted separately on its own server is 2 CPU Cores and 16 GB RAM.
- Benchmarked on Windows Server 2012 R2 Hyper-V infrastructure, with Database and Application Server components setup on separate VMs hosted on same physical host.
- CPU: Hyper-V Host CPU configuration - 2x Intel Xeon CPU E5-2867W v3 @ 3.10 GHz, 25MB Cache, 10C/20T, Max Mem 2133MHz.
- Network: Application server and Database server were connected over a 10Gbps link through a 10Gbps physical switch. External connections for the VMs were over a 1Gbps link through a 1Gbps physical switch.
- Database storage:
- Intel DC P3700 Solid State Drives (SSDs) with up to 450K/175K IOPS (4K random read/write QD32), and Samsung 850 PRO SSDs with up to 100K/90K IOPS (4K random read/write QD32), attached locally to the Hyper-V host.
- MDF, LDF and TempDB files on separate disks, with MDF on Intel DC P3700 SSDs, and LDF and TempDB on Samsung 850 PRO SSDs.
Physical or VM
- The servers can be deployed either on physical or virtual machines. For deployment on a virtual machine, the CPU cores should be assigned at 100% virtual machine reserve.
- For a remote (split) server configuration, the Tachyon Server requires a dedicated network interface (MAC Address and IP Address) for connection to the remote SQL Server instance used for the Responses database.
- This dedicated SQL connection must be at least 1Gbps for Lab, Small and Medium environments (< 100000 devices) and at least 10Gbps for Large environments (> 100000).
- Split Data, Log and TempDB on separate disks for medium and large configurations.
- SQL Server must be configured with maximum server memory limit and not left at the default setting to consume unlimited memory.
- For sizing the Database server in the recommendations above, 4GB RAM has been added for the operating system on top of SQL Server instance RAM requirements.
In previous versions of Tachyon, you may have had to increase the UploadBatchSize value to 600 (default 300) in the Master database SwitchConfiguation table. This version of Tachyon does not require this configuration. If you changed this value in a previous version and have upgraded to the latest version of Tachyon, then you do not need to reset or change the value again.
AWS Network Configuration
For a split server installation it is necessary to configure an additional network interface into each server to guarantee a dedicated 1Gbps network channel between the core and the database. Enhanced networking (SR-IOV) must be enabled on both of these NICs which should be the default. Detailed steps on how to verify this are given here - http://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/sriov-networking.html. Also increase the transmit (TX) and receive (RX) buffer sizes to their maximum under the network adaptor advanced properties.
Azure Network Configuration
For a split server installation it is necessary to configure an additional network interface into each server to guarantee a dedicated 1Gbps network channel between the core and the database. Enhanced networking (SR-IOV) must be enabled on both of these NICs where this is available (only on instances with 8cores or more) and must be enabled during instance creation. The additional NIC must also have accelerated networking enabled using Azure Powershell or Azure CLI. Detailed steps on how to configure this are given here - https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-create-vm-accelerated-networking. Also increase the transmit (TX) and receive (RX) buffer sizes to their maximum under the network adaptor advanced properties within the guest OS.
If connecting to an Azure based Tachyon switch via external public Azure IP addresses or Azure Load Balancers you will need to extend the default TCP timeout from 4 seconds to 15 seconds - Detailed steps on how to do this can be found here - https://azure.microsoft.com/en-us/blog/new-configurable-idle-timeout-for-azure-load-balancer/
AWS Database Storage Configuration
Database instances (either combined or the database server in a split implementation) should use an additional Throughput Optimized SSD (ST1) EBS volume to guarantee sufficient disk performance. This is used for all database storage - data, log and tempdb. The specified instances do not support any more than one EBS volume. If you wish to separate data, log and tempdb onto separate volumes (as per Microsoft recommendations) you will need a higher spec instance for the DB server, one that will allow you to attach more volumes and allow higher throughput to disk.
For any implementation other than Lab the Elastic Block Storage (EBS) optimization must be enabled, either when the instance is originally launched or afterwards. Details on how to do this can be found here: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSOptimized.html.
Azure Database Storage Configuration
Database instances (either combined or the database server in a split implementation) should have a minimum of 2 SSDs for database files. One for the Tachyon data files and tempdb and the other for the log files.
Disable caching on the volume used for the SQL log drive. This is done on the Azure console and not within the guest. Remember to restart the DB server VM once this is changed.
Do not use geo-redundant storage for any of the SQL drives.
A full list of optimizations for running SQL on Azure is available here: https://docs.microsoft.com/en-us/azure/virtual-machines/windows/sql/virtual-machines-windows-sql-performance