Contact & Support

We are on standby to assist.

To discuss how NitroAccelerator can improve your ROI, please schedule a call with our CPO.

Point of Contact
Email: [email protected]
Schedule a Call
Customer Support
Email: [email protected]
Phone: +1.512.501.5254
System Requirements
Setup Guide
Troubleshooting

Frequently Asked Questions

If I have NitroAccelerator installed on a client or server, will I still be able to connect to a client/server that does not have NitroAccelerator installed?

Yes. NitroAccelerator does not affect any connections with non-NitroAccelerator clients or servers. However, you will only get the optimization benefit on connections that have NitroAccelerator installed on both ends.

How does licensing work?

Licensing and purchase information can be found on our GitBook.

Does it work on Linux?

NitroAccelerator only installs to Windows machines. However, it is possible to reduce latency by using a Linux system as an endpoint with Nitro installed to a Windows system as a proxy. (PDF Instructions)

Is NitroAccelerator cluster aware?

Yes. To run NitroAccelerator on a cluster, simply install the product on each node. On failover, your clients will continue to benefit from a compressed connection.

What is the CPU overhead when using NitroAccelerator?

This will depend on the compressibility of your data, but we typically see overhead in the range of 1-3%.

Will NitroAccelerator run on a virtual server?

Yes, NitroAccelerator can be run on a virtual machine.

Will NitroAccelerator speed up my backups?

NitroAccelerator only accelerates transmission protocols, and so will not impact non-transmission backup speeds. Backups to the cloud experience a significant throughput benefit.

Maintenance

What is HyperCache?

HyperCache is a client-side caching technology that can further improve performance in certain environments. It works by monitoring each query to determine how stable the results are. When a given query is determined to have stable results, the client will be given results from the cache instead of waiting for the server’s response. The query is still sent on to the server so the cache can be refreshed, and if the results of a query ever change, the query entry is invalidated until the result set is again shown to be stable. Only result sets of 64k or less will be cached, so HyperCache will have the biggest impact in environments with smaller repetitive queries. The Cache Size setting in the console determines the total number of queries that can be cached, so this can be adjusted as needed for your environment.