For users of our Host Your Own subscription, whereby you provide your own AWS account details for the provision of Gridinit nodes, there’s a neat trick via AWS Billing which lets you tag and allocate costs for different Grid nodes under your account. A simple use case is where a Test Agency wants to track usage of … Continue reading »
Announcing the first major pre-release version of the Gridinit JMeter DSL
For some time now, we’ve been beavering away on the first major version of our popular DSL for JMeter available as the Ruby gem gridinit-jmeter. In fact since we released the gem in November 2012 it’s been downloaded over 5000 times as well as people contributing to the code base with suggestions and improvements. We … Continue reading »
JMeter *does* provide consistent results
The problem with benchmarks is that generally “all competitive benchmarking is institutionalized cheating.” The purpose of competitive benchmarking a computer system is to beat everyone else on performance, so you can say “mine is bigger than yours.” It’s the IT equivalent of war! Benchmark run-rules were made to be broken or at least bent; just … Continue reading »
High Concurrency JMeter Tests
Concurrency, what is it? It can simply be defined as The property of systems in which several computations are executing simultaneously, and potentially interacting with each other. Concurrency is often used to define workload for load testing, as in concurrent users. Too often it’s the only input defined. In reality there are a number of … Continue reading »
How to Load Test a Rails App with Gridinit-JMeter
Introduction These introductory guides are designed to help you script realistic load test scenarios using the gridinit-jmeter ruby gem. In this guide we highlight some of the common areas which need to be catered for when load testing a typical rails application. This is a start to things like keeping track of sessions, CSRF token handling and submitting forms. … Continue reading »
Testing HTTP APIs with Gridinit JMeter
We’ve been busy refactoring and adding to our open source gem gridinit-jmeter which lets you write test plans in Ruby, for JMeter. Being open source we’ve also had contributions from hiroyuki-sato and markma0121. Thanks guys! Even better, we’ve had almost 2,000 downloads of this gem in just 3 months, which we think is pretty special for a gem … Continue reading »
Persist Test Results with Elasticsearch
A key to Gridinit’s success is keeping things simple. Our Grid nodes effectively follow a shared-nothing architecture. This keeps the Grid operating costs low, and your prices extremely competitive compared to today’s load testing solutions. Whenever you purchase a Grid node on demand, or host on your own AWS account, each node includes its own instance of … Continue reading »
Filtering Test Results
So you’ve been running some tests and you find that there’s some results you’d like to filter in or out of your test results, without rolling your own charts? Gridinit makes this easy to do with the use of a filter query parameter. We often use this approach hence why we name individual sampler labels … Continue reading »
Creating and Sharing Test Data on the Grid
Most test plans will depend on some form of static data. Traditionally this would be done via some form of external CSV formatted file. In some cases it’s important to share test data between threads. Guaranteeing uniqueness of data between threads and between different load generators becomes problematic. Gridinit has created a custom JSON API for you to upload, manage and access … Continue reading »
News from the Grid December 2012
Simple and Affordable In the lead up to Christmas we’ve been busy enhancing features and making sure the Grid is a simple and affordable alternative for load testing. Some of the recent features include: Writing Test Plans in Ruby. If you’re tired of using the JMeter GUI or looking at hairy XML files then we have an elegant solution for … Continue reading »
