Product documentation
Citrix Virtual Apps and Desktops
Current Release Service 2511 2507 LTSR 2503 2411 2407 2402 LTSR 2311 2203 LTSR
View PDF

Log Server Recommendation

June 8, 2026
Contributed by: 
C

Daily Log Volume (Storage)

Item Number of Machines Sessions per Day/Machine Avg. Log Size per Session Total Logs per Day
Persistent VDAs 1000 2 2 MB 4,000 MB (≈4 GB)
Pooled VDAs 1000 50 2 MB 100,000 MB (≈100 GB)
CWA Endpoints 8000 4 1-1.5 MB 48,000 MB (≈48 GB)
Delivery Controllers 4 — 300 MB per DDC 1,200 MB (≈1.2 GB)
StoreFront Servers 4 — 300 MB per server 1,200 MB (≈1.2 GB)
NetScaler Gateway /PVS/Session Recording/ FSA and other servers 4 — 300 MB per server 1,200 MB (≈1.2 GB)
Daily Total Log Size (Post Compression) — — — Before compression is ≈156 GB/day
        Post compression is 80 GB to 125 GB/day

Sizing Assumptions

  • This example represents a reference deployment of approximately 10,000 managed endpoints and infrastructure components.
  • For sizing purposes, Delivery Controllers, StoreFront servers, Gateway, PVS, FAS, Session Recording, and other infrastructure components are estimated at 300 MB per server per day.
  • The 300 MB per server value is a conservative estimate used for storage planning and capacity calculations.

Note:

  1. These values are approximate and can differ widely between deployments. Log volume depends on site size, user activity, component mix, and retention needs. Use these numbers only as a baseline to begin planning and adjust the storage allocation based on your environment’s actual usage, growth trends, and performance testing.

  2. Log server uses the LZ4 compress algorithm by default. The compression percentage could be between 20% to 50%; it means LogServer would take half of the disk space when it does the maximum compression or 80% disk space when it does the minimum compression.

  3. A single AOT Log Server can support up to 128,000 active component connections and process up to 10,000 log events per second. The Log Server is designed to continuously collect and store AOT logs around the clock, provided the environment remains within these connection and throughput thresholds.

  4. These recommendations are driven not by the size of the virtual machine, but by the capacity of the underlying search and indexing engine that ingests, processes, and stores incoming AOT logs. This search layer ultimately determines maximum scale because it handles indexing, querying, and retention operations. As environments grow, this layer must scale horizontally to maintain performance.

  5. Today, the Log Server ships as a single combined node that includes both the Log Server service and the search/index engine. This simplifies deployment but limits the ability to scale the search tier independently.

  6. In upcoming releases, Citrix will transition to a separated architecture, where ingestion and storage/indexing run on independent nodes. This will allow customers to scale the search tier as their environment grows, improve performance across large or multi-site deployments, and remove the scalability ceiling imposed by the current single-node design.

  7. Deploy the AOT Log Server on SSD-backed storage. SSDs are strongly recommended to ensure reliable log ingestion, fast search performance, and efficient correlation, especially in high-volume environments.

AOT Log Server Storage Sizing

Sizing storage correctly is one of the most important steps when planning the AOT Log Server. The total storage required depends on how many machines are sending AOT logs, how much data is generated per day, and how long logs must be retained.

Because each Citrix environment behaves differently, customers should begin by estimating their daily log volume using the log generation patterns of their VDAs, Citrix Workspace App endpoints, Delivery Controllers, and StoreFront servers. Once the daily volume is known, the total storage can be calculated using the formulas below.

Storage Calculation Formula Total Storage (GB) = Daily Log Volume (GB) × Retention Days

AOT Log Server Storage Sizing Guidance

Use the following table as a reference for estimating daily log volume and storage requirements based on deployment size. These estimates are intended for capacity planning and may vary based on user activity, session density, enabled components, and deployment architecture.

Daily Log Volume Estimate

Deployment Size Daily Log Volume Before Compression Daily Log Volume After Compression (LZ4) Recommended Category
5,000 machines ~78 GB/day ~40–63 GB/day Small
10,000 machines ~156 GB/day ~80–125 GB/day Medium
50,000 machines ~780 GB/day ~400–625 GB/day Large
100,000 machines ~1.56 TB/day ~800 GB–1.25 TB/day Enterprise

Retention-Based Storage Estimate

Deployment Size 7-Day Retention 10-Day Retention
5,000 machines ~300–450 GB ~400–630 GB
10,000 machines ~600 GB–1 TB ~800 GB–1.25 TB
50,000 machines ~3–5 TB ~4–6.3 TB
100,000 machines ~6–10 TB ~8–12.5 TB

Note:

  • These values are approximate estimates intended for capacity planning. Actual storage requirements depend on deployment architecture, user activity, enabled components, retention period, and compression efficiency.

  • Estimates are based on the 10,000-machine reference deployment model and scaled linearly.

Log Server Recommendation
June 8, 2026
Contributed by: 
C
June 8, 2026
Contributed by: 
C

In this article

Site feedback | Your privacy choices footer linkYour Privacy Choices | Privacy and legal terms | Cookie preferences | Consent settings | docs.cloud.com
© 1999- Cloud Software Group, Inc. All rights reserved.