Performance testing used to be an optional aspect for most applications — something you did at the end, if you had time and you really cared. Now, it’s a must. User expectations today are much more sophisticated (you compete not only within your industry; your app is compared with everything else users experience online), and software is becoming more complex, with many third-party components deployed over cloud infrastructure. And this is not limited to the performance of your app. Your development process needs to be fast and agile to guarantee a faster time to market and rapid response to customers’ needs.
The holidays are a busy time for many companies. And while that brings an exciting window of opportunity, it can also mean also more challenges to be prepared for.
More traffic on a website is good, but will your infrastructure be good enough for it? And your software? Is there a way to find it out before it hits your application or website? And how can you know before the next holiday rush?
Did you know that 52% of the Fortune 500 companies have disappeared in the past 15 years? Why? Life expectancy for the enterprise is getting shorter. In 1955 the average life expectancy was 75 years. In 2015 is 15 years. Why these changes? Because the world has evolved and transformation happens at a much faster speed than 50 years ago or even 20 years ago. And if enterprises don’t adapt, they simply vanish.
What is really impactful to the user experience is the transaction time.
As we’ve covered in previous posts, performance testing is different from functional testing, and therefore requires different criteria when setting goals, creating test plans, and evaluating results.
Often times, the degree of complexity in the workflow of a functional test is not required to create a meaningful performance test scenarios. The focus is not on what is working (or not), but how the load affects the system under test.
Still, there are several aspects that can play a crucial role when generating load, which necessarily require a certain complexity in performance testing scenarios.
How do I create a test?
It is very easy to create a test in Nouvola DiveCloud. No scripting is required, and you can build and run a test in less than five minutes. The test plan is a very simple form, pre-filled with recommended values, and suggestions on how to change them.
Our customers are often asking questions about the Nouvola product infrastructure and how it works. Since there are several recurring questions, we wanted to share the answers with all our readers.
Change your mindset to change to DevOps
The IC3 conference is always a good opportunity to keep up with the latest in the IT and DevOps world. This year’s Fall event was set in San Jose, in the heart of the Silicon Valley, and attracted a great crowd eager to learn more about cloud solutions, and also to share tips and stories.
The conference’s Executive Track focused on how to create high-performing teams, and on the role of IT and DevOps.
“High-performing IT” (and how to get there) was also the title and the topic of the panel moderated by Bernard Golden, a true expert in cloud computing. I had the privilege of joining him, alongside Asya Kamsky (MongoDB), Mallika Iyer (Pivotal), and Thomas Goepel (HP). The following is a recap of some of the key points and takeaways from our discussion.
Last year we introduced you to Nouvola co-founder and CEO Paola Moretto. Here, meet co-founder and chief technology officer Paola Rossaro.
Third in a series on how to effectively use Nouvola DiveCloud
Earlier this year, we talked about the best way to calculate concurrent users when using Nouvola DiveCloud, and touched on the importance of performance tests to let you know how much traffic your software can handle with the right speed. We also defined Virtual users, sessions and concurrent virtual users.
Now, let’s take a look at all the timing options in Nouvola DiveCloud.