DOOZ: Controlled Load-Test Technical Quality Benchmark
A precisely scoped technical benchmark using the approved DOOZ load-test response counts—without production-capacity or SLA claims.
The challenge
DOOZ required a controlled technical quality benchmark that could document response outcomes under load without exposing customer-sensitive endpoints or overstating the result as real-world capacity.
The solution
Dfeelings executed and documented a controlled load-test run, then separated successful HTTP responses from socket and connection timeouts. Only approved aggregate response counts are published.
Scope & implementation highlights
Load-test execution, aggregate response classification, success-rate verification, limitations review, and a publication-safe technical summary.
Implementation process
The approved summary confirms the virtual-user target and aggregate sample outcomes. Ramp-up profile, request mix, tool, test date, and environment identifier are not present in the approved evidence available to this repository and are not inferred.
Verified for publication
Results
Every number below is published with its result type, measurement period, source, and methodology.
Load-test technical benchmark
500virtual users
Virtual users
- Measurement period
- Single controlled load-test run; exact date not recorded in the approved summary available here
- Source & methodology
- Approved DOOZ load-test report summary. Virtual-user count confirmed by the approved report summary.
Load-test technical benchmark
6000samples
Total samples
- Measurement period
- Single controlled load-test run; exact date not recorded in the approved summary available here
- Source & methodology
- Approved DOOZ load-test report summary. Aggregate sample count confirmed by the approved report summary.
Load-test technical benchmark
5886responses
HTTP 200 responses
- Measurement period
- Single controlled load-test run; exact date not recorded in the approved summary available here
- Source & methodology
- Approved DOOZ load-test report summary. HTTP 200 response count in the approved summary.
Load-test technical benchmark
88responses
SocketTimeout
- Measurement period
- Single controlled load-test run; exact date not recorded in the approved summary available here
- Source & methodology
- Approved DOOZ load-test report summary. SocketTimeout response count in the approved summary.
Load-test technical benchmark
26responses
ConnectTimeout
- Measurement period
- Single controlled load-test run; exact date not recorded in the approved summary available here
- Source & methodology
- Approved DOOZ load-test report summary. ConnectTimeout response count in the approved summary.
Load-test technical benchmark
98.1%
HTTP 200 response rate
- Measurement period
- Single controlled load-test run; exact date not recorded in the approved summary available here
- Source & methodology
- Approved DOOZ load-test report summary. Calculated directly from approved counts: 5,886 ÷ 6,000 × 100, rounded to one decimal place.
The controlled run recorded a precisely calculated 98.1% HTTP 200 response rate. This is a single controlled load-test benchmark, not total production capacity, an SLA, or a guarantee that mobile-app and website APIs are identical.
Technologies
Related services & pages
Related case studies
Dfeelings
Dfeelings.com: A Bilingual, CMS-Driven Digital Platform
View case study
Confidential – Jordanian FinTech Company
Jordanian FinTech Startup Raises Series A After Brand Identity Overhaul
View case study
Confidential – Amman Residential Developer
Jordan Real Estate Developer Cuts Time-to-Sale by 40% With 360° Virtual Tours
View case study