Class Win32AssociatedProcessorMemoryService

java.lang.Object
io.github.eggy03.ferrumx.windows.service.processor.Win32AssociatedProcessorMemoryService
All Implemented Interfaces:
CommonServiceInterface<Win32AssociatedProcessorMemory>
public class Win32AssociatedProcessorMemoryService extends Object implements CommonServiceInterface<Win32AssociatedProcessorMemory>
Service class for fetching the association between a Processor, and it's Cache information from the system.

This class executes the Cimv2.WIN32_ASSOCIATED_PROCESSOR_MEMORY PowerShell command and maps the resulting JSON into an immutable list of Win32AssociatedProcessorMemory objects.

Usage examples

// Convenience API (creates its own short-lived session)
Win32AssociatedProcessorMemoryService service = new Win32AssociatedProcessorMemoryService();
List<Win32AssociatedProcessorMemory> apm = service.get();

// API with re-usable session (caller manages session lifecycle)
try (PowerShell session = PowerShell.openSession()) {
    Win32AssociatedProcessorMemoryService service = new Win32AssociatedProcessorMemoryService();
    List<Win32AssociatedProcessorMemory> apm = service.get(session);
}

// API with execution timeout (auto-created session is terminated if the timeout is exceeded)
Win32AssociatedProcessorMemoryService service = new Win32AssociatedProcessorMemoryService();
List<Win32AssociatedProcessorMemory> apm = service.get(10);

Execution models and concurrency

This service supports multiple PowerShell execution strategies:

  • jPowerShell-based execution via get() and get(PowerShell):
    These methods rely on jPowerShell sessions. Due to internal global configuration of jPowerShell, the PowerShell sessions launched by it is not safe to use concurrently across multiple threads or executors. Running these methods in parallel may result in runtime exceptions.
  • Isolated PowerShell execution via get(long timeout):
    This method doesn't rely on jPowerShell and instead, launches a standalone PowerShell process per invocation using TerminalUtility. Each call is fully isolated and safe to use in multithreaded and executor-based environments.

For concurrent or executor-based workloads, prefer get(long timeout).

Since:
3.0.0