Acumatica登录及库存列表加载缓慢问题及IIS预加载配置求助

Is the observed performance normal? #

First off, let's break down your two performance scenarios:

1. Initial login delay (13 seconds)
   This isn't totally out of the ordinary for the first login after the application pool starts or recycles. The lag comes from Acumatica spinning up all its core components—compiling ASP.NET views, loading metadata, initializing database connections, and any customizations you have running. That said, 13 seconds is a bit long given your solid hardware (i7-4790K, SSD). You can trim this down by:

• Ensuring view precompilation is enabled (check your web.config for compilation debug="false"—debug mode disables precompilation and slows things down)
• Disabling any unused customizations or plugins that load on startup
• Making sure your SQL database (local or remote) has proper indexing and isn't under unnecessary load

2. 1000-item inventory list load (16 seconds)
   This depends heavily on your setup. If the list includes custom calculated fields, complex filters, or row-level security rules, that delay might be expected. But if it's a vanilla inventory list without extra frills, 16 seconds is definitely slow. Things to investigate:

• Missing indexes on key inventory tables like InventoryItem
• Heavy business logic that triggers when loading the list
• Network latency if your SQL server is on a remote machine

In short: The initial login delay is common but can be optimized, while the list load time might need deeper digging if you're running a standard setup.

Fixing the Application Initialization preload URL issue #

The W(...) string in your URL is ASP.NET's cookieless session ID—Acumatica uses this when it can't store sessions in cookies, which is why the number changes randomly. Here are three reliable fixes:

Option 1: Force cookie-based sessions #

Edit your Acumatica web.config file:

• Locate the <sessionState> section
• Update it to prioritize cookie-based sessions:

  <sessionState mode="InProc" cookieless="UseCookies" timeout="20" />
  

This will store the session ID in a cookie instead of the URL, so your preload target won't have that dynamic W(...) segment anymore.

Option 2: Use Acumatica's built-in warm-up page #

Acumatica has a dedicated warm-up endpoint that doesn't require a session. Use this as your preload URL:
/AcumaticaERP/WarmUp.aspx
This page is designed specifically to initialize the application without creating a session, so no dynamic URL segments will be generated.

Option 3: Tweak IIS preloading settings #

1. Open IIS Manager and navigate to your Acumatica site
2. Go to Advanced Settings and set Preload Enabled to True
3. For your application pool, set Start Mode to AlwaysRunning
4. Use either the root URL (/AcumaticaERP/) (if you went with Option 1) or the /WarmUp.aspx endpoint (from Option 2) as your preload target

Any of these methods will let you set a static preload URL that stays consistent.

内容的提问来源于stack exchange，提问作者JM_caveman