본문으로 건너뛰기
게임 · 리뷰 · 데이터베이스
포럼

CPU Core Affinity and Hybrid Architecture Scheduling: Intel P-Cores vs E-Cores: Advanced Implementation and Real-World Architecture

홈 › Forums › Global Gamer Lounge & Matchmaking › General PC 게이밍 & Industry Discussions › CPU Core Affinity and Hybrid Architecture Scheduling: Intel P-Cores vs E-Cores: Advanced Implementation and Real-World Architecture

Viewing 1 post (of 1 total)
  • Author
    Posts
  • #126983
    User AvatarIsaac Wright
    Member

    I’ve been running stress tests on my i9-13900K for competitive titles, and I’m hitting some real scheduling inconsistencies. When I pin my game thread to dedicated P-cores via SetThreadAffinityMask and disable Thread Director’s autonomy through ELS (Efficient-Little-Stack) partitioning, I’m seeing periodic micro-stutters in ranked play that don’t show up in synthetic benchmarks. Has anyone else experienced Thread Director aggressively migrating threads onto E-cores mid-match despite explicit affinity masks, and what’s your workaround?

    Second question on the ring bus: I’ve read that off-die communication across the ring latency penalty gets worse when you spread threads across multiple core complexes. In a multi-monitor setup running overlay telemetry on separate cores, have you measured a real FPS impact from that cross-die traffic, or is it negligible at 1080p? And how do you handle background task pinning—do you dedicate a full P-core cluster to OS/capture threads, or is splitting them across E-cores fine to preserve headroom for the game thread? Would love actual benchmark numbers, not just anecdotes.

    gamer@rig:~$ nvidia-smi –query-gpu=temperature.gpu,power.draw –format=csv
    "54 C, 185.4 W (100% load stable)"
Viewing 1 post (of 1 total)
  • You must be logged in to reply to this topic.

Gamer24H 검색

3자 이상 입력하세요.

탐색

디자인 설정

테마 색상 선택

자동 mode follows your device and switches to Xbox, PlayStation, or Nintendo colors on matching stories. Your manual choice stays on this device.

🌍 언어 선택 25 개 언어
🔍