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

Log Server Recommendation

December 10, 2025
Contributed by: 
C

Daily Log Volume (Storage)

Item Value Sessions per Day 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 7500 4 1 MB-1.5 MB 45,000 MB (≈45 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 ≈155 GB/day
        Post compression is 80 GB to 125 GB/day

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.

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

Example Calculation - Daily Log Volume (post compression) = 125 GB – 200 GB) The following example illustrates how storage requirements scale for different retention targets.

Retention Period Storage Required
7 days 560 GB – 875 GB (Recommended)
15 days 1,200 GB (≈1.200 TB) - 1,875 GB (1.875 TB)
30 days 2,4000 GB (≈2.400 TB) - 3,750 GB (3.750 TB)
Log Server Recommendation
December 10, 2025
Contributed by: 
C
December 10, 2025
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.