Frequently asked questions
What is Continuous Optimization?
Continuous Optimization is an advanced form of application performance tuning that measures, predicts and then implements parameter changes to your cloud-native application to optimize for cost or performance automatically.
Who uses Continuous Optimization?
Developers, DevOps, Performance Engineers and Operations teams use Continuous Optimization to take the guesswork out of running their applications at high performance and low cost.
What do you optimize?
We optimize cloud applications to achieve higher performance and lower cost. Applications are built in layers; most notably, the App layer (UI, application code, database schema), the Middleware (web server, JVM, DB), the OS (Kubernetes, Docker, Linux) and the Infrastructure (Cloud, VM, Network). Most optimization tools focus on the App layer and your code, but bottlenecks in the Middleware, OS and Infrastructure layers can have profound impact on performance and cost. We optimize your application performance by measuring things like requests per second and response time while tweaking hundreds of settings like VM instance type, CPU shares, thread count, garbage collection and memory pool sizes.
How is Continuous Optimization different from Application Performance Monitoring (APM)?
APM systems focus on monitoring applications, their transactions and reporting the results or triggering alarms when something goes wrong. Some go further to provide recommendations on what changes are necessary to reduce bottlenecks and increase performance. Continuous Optimization works in conjunction with APM. It continuously measures, predicts (through machine learning) and implements small changes to get your app to its optimal state.
What is Opsani?
Opsani is a continuous optimization system that increases application performance and reduces cost by leveraging machine learning to adjust resource assignments and configuration settings automatically. Using Opsani takes the guesswork out of balancing requirements, cost and performance.
Why do I need Opsani?
Humans can only do so much to keep up with the complexity of modern applications. A simple five container application can have more than 255 Trillion resource and basic parameter permutations. In addition to the enormous number of configuration tweaks that can be made, your developers are releasing new features, your middleware is getting updates and your cloud vendor is releasing new resource options. This is where Opsani comes in, taking the guesswork out of optimizing your application for performance and cost while eliminating work for you.
What does Opsani do?
Opsani runs as a service taking in metadata about your application, making small tweaks to resource assignments and configuration settings to enhance performance or reduce cost and then continuously remeasuring whenever changes are made. It does this quickly and effectively in the background while you work. Typically, in hours you’ll start to see benefits.
What kind of results should I expect?
Customers have seen a 2.5x increase in performance or a 40-70% decrease in cost overnight on an “already tuned” application.
How quickly will I see results?
Depending on your application you could see improvement in just a few hours after implementation. After the initial period Opsani continues to search for optimal settings as you release new code or apply patches to middleware.
How long does Opsani take to implement?
Our team currently works with users to implement Opsani at each site. Usually it takes a meeting or two to learn about your application and a few hours for our team to configure Opsani within your app environment.
Do I have to run Opsani in production?
Opsani can run in development, testing or production environments. Ideally, running in production allows Opsani to adjust for how your application is actually used and eliminates the need for complex traffic generation in staging.
Need additional support?
Send us an email if you require additional assistance after consulting the documentation and FAQ’s.
Opsani is on GITHUB
Once you have started the on-boarding process with us you can find our repository of drivers on GitHub. Drivers are always being developed. So let us know if you need one specific to your environment.