Citrix DaaS · /// Cloud-Hosted Citrix Validation

Citrix DaaS is still Citrix. Test it like it is.

LoadGen’s 7-step Citrix wizard works against Citrix DaaS (Citrix Cloud) the same way it works against on-prem Citrix. HDX + ICA capture, Cloud Connector latency awareness, Service Continuity validation — on Full agents, with transparent published pricing.

Validate Citrix DaaS at scale Talk to an engineer

Citrix Cloud-awareCloud Connector latency captured€1,099 / week · 50 → 25k vUsers

/New Citrix Profile

Mode: Basic Online

AD

admin

Administrator

New Citrix Profile

Step 1: Set profile name and Citrix type

Citrix Enhanced

Basics

Connection

Users & Agents

Display

Scenario

Advanced

Review

Profile Basics

Configure the basic settings for your Citrix load profile.

Profile Name *

A unique name to identify this profile

Profile Status

Profile is active

Enable or disable this profile

Citrix Type

DocumentationSupportCreate Ticket

7-step Citrix wizard — works against Citrix Cloud + Citrix DaaS.

The Problem

Citrix Cloud changes the topology, not the protocol.

Many teams migrating to Citrix DaaS assume the move to cloud means they need a different load-testing tool. They don’t. HDX is HDX; ICA is ICA. What changes is the broker topology, the Cloud Connector path, and the Service Continuity behaviour.

Cloud Connector adds latency.

The Cloud Connector forwards traffic between the cloud control plane and on-prem resource locations. Generic load tools don’t see the per-Cloud-Connector latency that actually drives Citrix DaaS user experience.

Service Continuity changes behaviour under broker outage.

When the cloud broker is unreachable, Service Continuity routes sessions via cached connection leases. The behaviour under simulated broker failure differs from on-prem Citrix — and needs to be measured.

Capacity sizing for cloud resource locations.

On-prem Citrix sizing models don’t map directly to Citrix DaaS resource-location sizing. Cloud Connector throughput, gateway PoP selection, and resource-location density all affect the answer.

Why LoadGen for Citrix DaaS

Same wizard. Citrix Cloud topology, captured.

The 7-step Citrix wizard handles Citrix DaaS configurations natively — Cloud Workspace URL, Cloud Connector resource locations, gateway PoP — and the scenario engine measures the Cloud Connector latency that actually drives Citrix DaaS user experience.

Citrix Cloud Workspace URL native

The wizard authenticates against Citrix Cloud Workspace the same way it authenticates against on-prem StoreFront — Basic and Enhanced modes both supported.

Cloud Connector latency captured

Per-step latency includes Cloud Connector round-trip — visible alongside HDX p95 and login time. The component that actually breaks first under measured load.

Same scenario, on-prem ↔ DaaS

The .lgs scenario that runs on on-prem Citrix runs unmodified against Citrix DaaS. Compare the two on the same scenario shape — what the cloud migration actually changed.

Live orchestration

Citrix DaaS, live, under measured load.

The cockpit your engineers will operate during a cutover weekend. vUsers ramping, Full-agent allocation per Resource Location, Cloud Connector latency — all live.

vUsers ramp across warm-up / steady / spike / cool-down — visible as the run progresses.
Full agents allocated per Resource Location — actual session-host pressure.
Per-step latency + HDX p95 + Cloud Connector round-trip bound to every scenario.
The same scenario shape powers live monitoring after cutover.

Load Profiles › Orchestration

Mode: BasicOnline

A

Load Profile · Workload Orchestration

Ramp-up · steady · spike · cool-down, scheduled across agents and scenarios.

Concurrent users

500peak 540

Current phase

Spike32 min elapsed

Agents allocated

148 · 4 · 2

Scenarios

3/5active / total

Ramp profile

vUsers · 60 min window

Warm-up

Steady

Spike

Cool-down

Agent pools

Core8

Full4

VDI2

Scenario queue

orchestrated

Citrix Finance · daily peak

240 vU

AVD Sales · sprint launch

160 vU

Web Storefront · soak run

100 vU

RDS Engineering · spike test

80 vU

Horizon HR · capacity sweep

60 vU

DocumentationSupportCreate Ticket

Live orchestration cockpit during a Citrix DaaS run.

Capability

What ships with Citrix DaaS performance validation.

7-step Citrix wizard

Basic (ICA) + Enhanced (HDX); Citrix Cloud Workspace URL native; Resource Location selection. Same authoring model as on-prem Citrix.

Learn more

Full agents for Citrix DaaS

Per-session Activate / Reset / Kill operations land on every Citrix DaaS session host. Real session-host pressure, not thread-based abstractions.

Learn more

Cloud Connector + Citrix Broker telemetry

SUT Monitoring binds Cloud Connector latency, Citrix Broker counters, StoreFront / Workspace dependencies to every test execution.

Learn more

Live cockpit, real-time KPIs

Per-step concurrency, Cloud Connector latency, HDX-channel health — visible as the test runs, not buried in a post-test report.

Learn more

AI-flagged DaaS anomalies

Analytics AI scores Cloud Connector latency drift, gateway-PoP routing anomalies, and per-step bottlenecks per execution.

Learn more

On-prem ↔ DaaS comparison

Same workload, both topologies. Compare HDX p95, login latency, Cloud Connector overhead side-by-side. What did the cloud migration actually buy you?

Learn more

Outcomes

Measured before / after on Citrix DaaS.

Time to first DaaS test

Before

5 days

After

4 hrs

−97 %

Auth-flow setup hours

Before

12 h

After

40 min

−94 %

Cloud Connector latency captured

Before

No

After

Yes

measured

Citrix-specific p95 captured

Before

Partial

After

Full

HDX + ICA

See it in action

Three Citrix DaaS surfaces.

Citrix wizard

Cloud Workspace URL + Resource Location.

/New Citrix Profile

Mode: Basic Online

AD

admin

Administrator

New Citrix Profile

Step 1: Set profile name and Citrix type

Citrix Enhanced

Basics

Connection

Users & Agents

Display

Scenario

Advanced

Review

Profile Basics

Configure the basic settings for your Citrix load profile.

Profile Name *

A unique name to identify this profile

Profile Status

Profile is active

Enable or disable this profile

Citrix Type

DocumentationSupportCreate Ticket

Live cockpit

Per-step latency, Cloud Connector round-trip.

Testing › Active Test › Run #847

Mode: BasicOnline

A

Active Test · Run #847

Streaming via SignalR · 12m 34s elapsed

Events/s

+4.2%

1,842

Concurrent

+312 vs base

2,847

Success

+0.2%

98.7%

Live Throughput

Events/sErrors/s−10m · −5m · now

Live Event Stream

SignalR · hub://loadgen/run/847

14:23:00.000POST /api/runs/events38msOK

14:22:59.767POST /api/alerts/check31msOK

14:22:59.534GET /api/dashboards/meta82msOK

DocumentationSupportCreate Ticket

Run comparison

On-prem Citrix vs Citrix DaaS overlay.

Testing › Results › Compare

Mode: BasicOnline

A

Test Analysis - Run Comparison

Overlay up to 5 runs to see performance deltas.

Compare Runs

·1 selected

Last 7 days

Citrix

Runs

Run #843Baseline

Run #844

Run #845

Run #846

Run #847

Avg Response

280 ms

P95 Latency

420 ms

Error Rate

0.12%

Throughput

1450/s

Response Time - Overlay

ms · 16 samples

Run #843 is the baseline

#843

DocumentationSupportCreate Ticket

Where Citrix DaaS validation lives

Three DaaS-specific testing windows.

On-prem → Citrix DaaS migration

Baseline on-prem Citrix; test target Citrix DaaS on the same scenario shape. Compare HDX p95, login time, and Cloud Connector overhead — sign the cutover with data.

See use case

DaaS Resource Location capacity planning

Measure session-host density per Resource Location. Right-size cloud compute, FSLogix share, and Cloud Connector throughput with evidence.

See use case

Release-gate DaaS performance proof

Wire LoadGen into the deploy pipeline. Block releases on HDX p95 regression or Cloud Connector latency drift — before production DaaS users notice.

See use case

Run your first Citrix DaaS load test in 4 hours.

Bring your Citrix Cloud Workspace URL and a workload sketch. We’ll author the .lgs scenario on a call, fire it from a managed Full agent, and show you HDX p95 + Cloud Connector latency — live.

Validate Citrix DaaS at scale View pricing

Questions

Frequently asked.

Does LoadGen test Citrix DaaS the same way it tests on-prem Citrix?

Yes — same 7-step wizard, same Full agents, same .lgs scenario format. The wizard handles Citrix Cloud Workspace URL natively; SUT Monitoring binds Cloud Connector latency and Citrix Broker counters automatically.

Can we compare on-prem Citrix performance against Citrix DaaS?

Yes. Author the scenario once; run it against on-prem Citrix, run it against Citrix DaaS. The cockpit overlays HDX p95, login latency, and Cloud Connector overhead side-by-side. The cloud-migration question becomes a data question, not an opinion question.

How does LoadGen handle the Cloud Connector?

SUT Monitoring binds Cloud Connector counters to every test — per-Connector latency, throughput, and error rate. Per-step latency in the cockpit includes Cloud Connector round-trip, so DaaS-specific overhead is visible alongside HDX channel pressure.

Does LoadGen test Service Continuity scenarios?

Service Continuity routes sessions via cached connection leases when the cloud broker is unreachable. Simulating that path requires deliberate broker-outage scenarios in test environments — we walk through how to design those on a call.

What does Citrix DaaS load testing cost?

€1,099 per week at the 50-vUser tier, scaling to 25,000 vUsers. Same published pricing as on-prem Citrix load testing — no DaaS-specific upcharge.

How long is the first Citrix DaaS test typically?

Same published target as on-prem Citrix: 4 hours from intake to first test result. Auth flow capture, scenario authoring, and a representative run.