TRAY logo transparent
Software

TRAY Boosts Enterprise POS System Efficiency and Reliability with Gatling Enterprise

Why Gatling Enterprise?

  • Manual performance testing took 3 days
  • 20,000 concurrent users used in performance testing
  • Response times reduced by up to 90%
  • Performance data analysis in hours
  • Gatling's accurate results enabled TRAY to replicate the production environment, allowing them to identify and resolve bottlenecks before deployment.
  • 200% improvement in API response

About TRAY

TRAY provides problem-free Point of Sale (POS) systems for restaurants helping enterprise restaurant brands create enjoyable experiences, by giving them the tools they need to run their multi-store operations all while allowing guests to order and pay how they want, when they want.

TRAY1

 

Statistics

Location: USA


Industry: Software > Restaurant POS Systems


Tech Stack: Java, SOAP / REST API, AWS Cloud, Circle CI


Business and Load Test Key Metrics:
30 distinct simulations in Java
Up to 20k concurrent users
Response Times reduced up to 90%


Gatling Enterprise Users: 6 developers

Start your free trial, see what Gatling can do for your team, and enhance your performance engineering.

“Gatling helps us maintain the data. It's easily extendable and easily scalable, which is an advantage compared to the previous tool.”
Henry Darana

QA Manager, TRAY

Challenges

Before adopting Gatling Enterprise, the TRAY QA team faced several significant challenges in performance testing:

Time-Taking endeavor to mimic production setup scenarios: Before using Gatling, TRAY found it time-consuming to replicate their geographically dispersed production environment, which involves multiple venues, locations, and brands. With Gatling, they can now accurately mimic their production setup with ease.

Performance Challenges with a Growing Number of Clients: As TRAY started serving larger clients with thousands of users across thousands of stores, they wanted to ensure consistent performance despite their growing client base. As TRAY continued to expand, performance became a major area of focus due to the increasing volume of transactions they handled each day.

Manual and Time-Consuming Processes: Before Gatling Enterprise, performance testing was a manual and time-consuming process, requiring up to three days to collect and analyze data.

Use Case/Solution

TRAY’s primary use case involves simulating the foundational flow of a staff member taking an order, authorizing a credit card, and completing the transaction. This process involves strenuously testing their user journeys with a concurrency of up to 20,000 users.

Load Testing: TRAY performs load tests to ensure their systems can handle peak user loads. For example, their "place order" flow was optimized significantly, reducing response times from 18-20 seconds to just 2 seconds.

Continuous Improvement: By integrating Gatling Enterprise into sprint cycles, they continuously monitor and improve API performance. This iterative approach has led to substantial performance gains, with some APIs showing up to 200% improvement in response times.

Improved Performance Testing Framework: Gatling's test-as-code approach, programming concepts and reusable components streamlined TRAY’s testing process, allowing them to write and run tests more efficiently.

Enhanced Reporting and Data Analysis: The detailed graphs and data tables provided by Gatling Enterprise made it easier to analyze performance metrics quickly. This reduced their data processing time from two days to just three hours.

Scalability and Auto-Scaling Capabilities: Gatling helped TRAY implement effective auto-scaling strategies, ensuring that their systems could handle high user loads without unnecessary resource expenditure.

Results

Place-Order and 40-Column-Report are TRAY’s most used scenarios. They run these scenarios/simulations for 200 users, with the goal of generating up to 20,000 concurrent requests. The numbers provided are the average response times of the scenarios/simulations. The decreasing time indicates an improvement in their response time.

TRAY results

Enhanced User Experience: The optimization of their systems has led to smoother and faster transactions, enhancing both customer satisfaction and employee efficiency.

Scalability and Cost Efficiency: Gatling's performance testing has enabled them to manage their resources better, avoiding unnecessary auto-scaling and reducing operational costs.



Utilizing chain builders with Gatling, what took days now takes hours. They aim to streamline their Gatling output to decrease this to 15 minutes. The detail and ease of access to the graphs and reports allows the TRAY team to monitor performance, identify areas for improvement and share data internally beyond just the QA team.

Gatling Enterprise has revolutionized their performance testing processes, providing TRAY with the tools to enhance their systems' efficiency, scalability, and reliability. The improvements they’ve seen since adopting Gatling have been substantial, positioning them well for future growth and success.

Future Plans

Looking ahead, TRAY aims to integrate Gatling Enterprise fully into their CI/CD pipeline using CircleCI, reducing test execution times to 15 minutes and ensuring continuous performance monitoring.

They also plan to expand their testing scenarios to cover more APIs and further improve their system's resilience and scalability. At present, TRAY runs 30 simulations every two weeks, moving forward they are looking to have over 100 simulations run through Gatling Enterprise regularly to ensure performance, stability and scalability.

Related Articles

From Our Blog

Stay up to date with what is new in our industry, learn more about the upcoming products and events.

Ghost Loads in E-Commerce Applications: Uncovering Hidden Performance Issues with Load Testing
Ghost Loads banner

Ghost Loads in E-Commerce Applications: Uncovering Hidden Performance Issues with Load Testing

Oct 30, 2024 7:45:00 AM 4 min read
Step-by-Step: Gatling Load Tests with TestContainers & Docker

Step-by-Step: Gatling Load Tests with TestContainers & Docker

Oct 2, 2024 11:50:30 AM 5 min read
Understanding workload models for load tests

Understanding workload models for load tests

Sep 26, 2024 8:30:00 AM 4 min read