Configuration Best Practices

This page lists the machine and instance settings recommended for local Haufe X360 development, and why each one matters.

⚡ IMPORTANT ⚡
These are recommendations for a comfortable local development experience, not hard requirements. A machine or instance that does not match every target below can still run Haufe X360 fine.

System

  • RAM - aim for 32 GB or more of total physical RAM. Between 16 and 31 GB triggers a warning, below 16 GB is flagged as an error.

  • CPU cores - at least 8 physical cores. Logical/hyper-threaded cores don’t count towards this.


Paths

  • Instance drive - keep the instance on an SSD-backed drive.

  • System drive - keep the instance off %SystemDrive% (usually C:) to reduce I/O contention.

  • Protected directories - keep the instance out of C:\Program Files, C:\Program Files (x86) and C:\Users. These are fixed paths on the C: drive rather than being derived from %SystemDrive%, so on a machine where Windows itself is installed on another drive, an instance can pass the system drive check above while still landing in one of these protected folders (or vice versa).


IIS (per instance)

The tool already configures all of the settings below automatically when it provisions an instance, so you shouldn’t need to touch any of this yourself. It’s here to help you recognize a setting that was changed afterwards, intentionally or not.

  • App pool start mode - AlwaysRunning, so the app pool stays warm instead of only starting on the first request.

  • App pool idle timeout - 200 minutes. IIS defaults to 20 minutes, which leads to frequent cold starts during development.

  • App pool recycling - no periodic or scheduled recycling, so you don’t lose in-memory state or sessions mid-session.

  • Site preload - enabled, so the site warms up immediately after an app pool start or recycle.

  • Site connection timeout - 1200 seconds. IIS defaults to 120 seconds, which is too short for long-running requests while developing or debugging.

  • App pool profile environment - setProfileEnvironment enabled, which the app pool identity needs in order to load its user profile/environment correctly.


Tool Dependencies

All dependencies required by X360 Developer Tool must be installed and version-matching. See Dependencies for the list of dependencies and how to install/update them.


SQL Server Configuration

⚡ RECOMMENDED ⚡
Running SQL Server inside WSL is the preferred setup for local development - it gives you a disposable, pre-tuned instance and avoids most of the manual tuning below. Prefer WSL over a native Windows SQL Server installation where possible; the checks and targets below only apply if you do run SQL Server natively on Windows.

  • Connectivity - a connection to the resolved SQL Server should succeed (read-only check).

  • Max server memory - at least 8192 MB, and at least 25% of total RAM. Left unconfigured, SQL Server can claim unbounded memory.

  • TempDB data files - 8 files, matching the SQL Server install default, to reduce TempDB contention.

  • Network protocols - TCP/IP and Named Pipes disabled. A local Haufe X360 instance only needs Shared Memory.

  • Collation - SQL_Latin1_General_CP1_CI_AS, matching the install default.

  • Full-Text Search - installed; required by some ERP features.

  • Instant File Initialization - enabled. This speeds up data/log file growth, but requires granting Perform volume maintenance tasks to the SQL Server service account (informational only, not auto-fixed).

Builds
Use Cases