G
G
Guides
Go to Dashboard
Search…
G
G
Guides
Getting started with Flood
Overview of Flood
What is load testing?
What is Flood?
Navigating Flood
Flood terminology
Scripting your load test
Designing your test
Launching your test
Executing your test
Analyzing results
Monitoring your grids
After your test
Scripting and Tools
Choosing a tool
Test Builder
JMeter
Gatling
Flood Element
Selenium
Default tool versions
Test data
Accessing the file system
Saving custom results
Custom libraries
Supported SSL ciphers
Infrastructure
Infrastructure overview
Demand infrastructure
Host Your Own infrastructure
Standalone Infrastructure: Flood Agent
Flood's network topology
Grid management
How to get the IP address of your grid node
Static IP addresses
Test Execution
Infrastructure
Test parameters
Advanced parameters
Environment variables
Baselining
Using the Flood API
Overriding DNS
Planning for a large-scale test
Troubleshooting: Test Execution
Results Analysis
Metrics during test
Flood options
Service Level Objectives
Archived Results
Sharing results
CSV Results
Troubleshooting: Results Analysis
Continuous Integration
Continuous Integration with Flood
Travis CI
Circle CI
Jenkins
APM Tools
Account Management
Managing account members
Managing account resources
Single Sign On (SSO)
Reset your password
Troubleshooting: Account Management
Pricing
How much does it cost?
What is a VUH?
Billing page
Usage page
Pricing FAQ
Why don't I see a VUH estimate?
Minimizing costs on Flood
Tosca
Using Tosca with Flood
Ebooks
API Load Testing: A Beginner's Guide
Powered By GitBook
Flood terminology
Defining projects, streams, floods, grids, nodes, and virtual user hours

As you progress with Flood, you may have multiple tests that you need to keep organized. Perhaps you've seen us refer to projects, streams and floods. All these words are buckets used to organize your tests. They don't really have a purpose other than to keep your Flood account easy to manage and to group related items together.
You can really use these buckets any way you want and group your tests in the way that makes the most sense to you. However, below is an explanation of the structure we recommend for most teams.
Projects > Streams > Floods
Projects correspond to real-life projects or releases. Let's say your project is called Flood Web Store. This project will contain all the different types of tests you have run that web store.
Streams are a little bit like test scenarios under projects. One stream under the project might be Login and Buy Shirt. Another stream might be Browse, where the user does not log in.
Floods are specific tests that fall under streams. A flood is an execution of a test scenario. Each time you run a test, that's a flood.
You can have several floods in the same stream, several streams in the same project and several projects in the same account.

Nodes are the machines that your flood runs on. Sometimes these are called load generators. They can be physical machines running on-premises or in your data center, but they can also be virtual machines that are provisioned for you on the cloud. Each Flood node has a unique IP address and runs anywhere from 1 to 1,000 virtual users, depending on the tool you're using.
A grid is a collection of nodes, and on Flood a grid can contain anywhere from 1 to 90 nodes. All nodes on a grid are in the same geographical region.
Two Flood grids in Frankfurt and California, containing 3 and 2 nodes respectively.
​
Previous
Navigating Flood
Next
Scripting your load test
Last modified 2yr ago
Copy link
On this page
Projects, streams, and floods
Grids and nodes