How to Use GetSystemInfo in Your Application

How to Use GetSystemInfo in Your Application

What GetSystemInfo does

GetSystemInfo retrieves basic information about the current system environment — CPU architecture, page size, processor count, and memory/addressing details — so your application can adapt behavior (threading, memory allocation, feature selection) to the host machine.

When to call it

Call GetSystemInfo at startup or when you need to make a platform-dependent decision (for example: choosing an optimal thread pool size or selecting code paths for 32-bit vs 64-bit addressing). It’s inexpensive and safe to call more than once if you expect the environment to change (rare on desktop/server but possible in some sandboxed/virtualized environments).

Platform note

This article assumes the Windows API GetSystemInfo (kernel32). Similar functions exist on other platforms (sysctl, uname, /proc/cpuinfo); adapt the concepts below if targeting non‑Windows systems.

Example usage (C, Windows API)

#include #include 
int main(void) { SYSTEM_INFO si; GetSystemInfo(&si); printf(“Processor Architecture: %u “, si.wProcessorArchitecture); printf(“Page Size: %u “, si.dwPageSize); printf(“Number of Processors: %u “, si.dwNumberOfProcessors); printf(“Processor Type: %u “, si.dwProcessorType); printf(“Allocation Granularity: %u “, si.dwAllocationGranularity); printf(“Lowest Application Address: %p “, si.lpMinimumApplicationAddress); printf(“Highest Application Address: %p “, si.lpMaximumApplicationAddress); return 0;}

Interpreting key fields

• wProcessorArchitecture: value indicates architecture (e.g., PROCESSOR_ARCHITECTURE_INTEL (0), AMD64 (9), ARM (5)). Use this to select architecture-specific code or optimizations.
• dwPageSize: memory page size in bytes — useful for aligning allocations or mapping files.
• dwNumberOfProcessors: logical processor count — use as a baseline for sizing thread pools; consider hyperthreading and workload characteristics.
• dwProcessorType: legacy numeric identifier; prefer wProcessorArchitecture for architecture decisions.
• dwAllocationGranularity: allocation granularity for VirtualAlloc/MapViewOfFile; align large allocation requests to this value.
• lpMinimumApplicationAddress / lpMaximumApplicationAddress: useful when implementing custom allocators or scanning virtual address ranges.

Practical tips

• For thread pool sizing: start with dwNumberOfProcessors and then test with your workload; I/O-bound apps may benefit from more threads, CPU-bound apps from roughly equal to cores.
• For memory mapping: align file mappings to dwAllocationGranularity and use dwPageSize for buffer alignment.
• When detecting 64-bit: check wProcessorArchitecture == PROCESSOR_ARCHITECTURE_AMD64 (9) or use IsWow64Process/IsWow64Process2 for more precise process vs OS bitness.
• Don’t rely solely on processor counts for performance decisions; measure throughput and latency under expected loads.
• Consider fallback behavior if fields contain unexpected values (e.g., treat unknown architecture as generic x86_64-compatible path).

Error handling and alternatives

GetSystemInfo does not return an error code; it always fills the SYSTEM_INFO structure. For more detailed OS/process bitness info use IsWow64Process or IsWow64Process2. On newer Windows versions, GetNativeSystemInfo returns native architecture for processes running under WOW64.

Cross-platform considerations

• Linux: read /proc/cpuinfo, sysconf(_SC_PAGESIZE), or use sysinfo(2) for RAM.
• macOS/BSD: use sysctlbyname(“hw.ncpu”), getpagesize(), or sysctl for architecture.
  Encapsulate platform-specific code behind an interface so application logic remains portable.

Security and stability

Do not expose raw SYSTEMINFO fields to untrusted inputs. Use retrieved values to tune behavior, not to alter security boundaries. Calling GetSystemInfo is safe and non-blocking.

GetSystemInfo is a simple, reliable way to detect host architecture, page size, and processor count. Use it at startup to tune thread pools, memory alignment, and platform-specific code paths, and pair it with other APIs (IsWow64Process, sysctl, sysconf) for more precise environment detection.