Implement automatic memory channel detection for optimized parallelization

[konard]

🎯 Summary

This enhancement addresses issue #34 by implementing dynamic detection of memory channels instead of hardcoding the thread count to 2 for memory zeroing operations in MemoryBlock.Zero.

💡 Problem Solved

Previously, the MemoryBlock.Zero method hardcoded the thread count to 2 based on the assumption that "two-channel memory architecture is the most available type." This approach wasn't optimal for systems with different memory configurations (single-channel, quad-channel, or higher).

✨ Key Features

Memory Channel Detection

• Windows: Uses WMI Win32_PhysicalMemory to query InterleaveDataDepth property
• Cross-platform: Falls back to estimating based on memory device count
• Intelligent fallback: Defaults to 2-channel assumption when detection fails
• Resource-aware: Always respects ProcessorCount / 2 limitation to prevent resource waste

Implementation Details

• Added MemoryChannelCount property to expose detected channel count
• Lazy initialization with caching for performance
• Platform-specific detection using proper OS platform checks
• Comprehensive error handling with graceful fallbacks

🧪 Testing

• Unit Tests: 13 tests covering channel detection, consistency, and memory zeroing functionality
• Benchmark Tests: Performance testing for both memory zeroing and channel detection
• Cross-Platform: Tests validate behavior on different platforms

📊 Performance Benefits

• Optimizes thread count based on actual memory architecture
• Better utilizes memory bandwidth on systems with more memory channels
• Maintains efficient operation on single/dual-channel systems
• No performance regression on existing systems

🔧 API Changes

New Public API

public static int MemoryChannelCount { get; }

Behavior Changes

• MemoryBlock.Zero() now uses detected memory channels instead of hardcoded 2 threads
• Thread count is still capped by Environment.ProcessorCount / 2 for resource efficiency
• Maintains backward compatibility - no breaking changes

📋 Test Results

All 13 unit tests pass, including:

• Memory channel detection validation
• Cross-platform compatibility
• Memory zeroing correctness with detected channels
• Processor count limitation respect

🔗 References

• Fixes Do we need to calculate the number of threads here based on number of memory channels available on motherboard? #34
• Uses WMI PhysicalMemory InterleaveDataDepth as requested in issue comments
• Follows LinksPlatform coding conventions and patterns

🤖 Generated with Claude Code