Proof of Concept (POC)
During your POC, we recommend activating NitroAccelerator on as many relevant endpoints as possible for a period long enough to measure quantitative impact.
Last updated
During your POC, we recommend activating NitroAccelerator on as many relevant endpoints as possible for a period long enough to measure quantitative impact.
Last updated
After requesting a trial, you will receive everything you needed to get started and the Nitrosphere team will send you an email to assist and ensure that accelerated connections form. Next, tuning recommendations will be offered to match your specific architecture and goals.
The trial length can be extended upon request and the countdown does not start until the time of install: https://nitrosphere.com/request-download/
High-priority IT Support Ticket counts
Bandwidth usage and cloud fees
Hardware & bandwidth upgrade time horizon
Queries Per Second (QPS)
Transactions Per Second (TPS)
Throughput (MB/sec)
Server I/O wait-time
Replication Backlog
Page load time
Application performance
File Transfer and data transmission speed
The NitroAccelerator Speed Test pings one of our test servers to run a few test queries. The purpose is to give you an estimate of the acceleration benefits that the software will have on your environment with default settings. We chose a simple Cartesian join because it mirrors the most accurate estimate of acceleration that our customers typically experience.
When your speed test completes, you will be asked if you want to share the results with the Nitrosphere team to assist with tuning and feature recommendations.
Use SSMS to run a representative query from your application both with and without Nitro.
Measure application load time and common processes/queries.
Longer term testing is often recommended for the majority of use cases. The HyperCache feature learns and improves over time and helps dramatically accelerate chatty applications during traditional use.
Measure Replication backlog decrease over time.
Monitor for decrease in server I/O wait times and congestion.
The Nitro team recommends collecting quantitative test data and is here to help with your proving process. Below is an example result.