Skip to content

First Version of Intel PCT Getting Started#37

Open
louie-tsai wants to merge 5 commits into
intel:mainfrom
intel-ai-tce:pct
Open

First Version of Intel PCT Getting Started#37
louie-tsai wants to merge 5 commits into
intel:mainfrom
intel-ai-tce:pct

Conversation

@louie-tsai

@louie-tsai louie-tsai commented Jun 23, 2026

Copy link
Copy Markdown

Guide users how to check PCT status and configure PCT for their workloads such as AI inference using vLLM

The Getting Started matches the contents of Intel PCT tech article.
https://www.intel.com/content/www/us/en/content-details/846906/priority-core-turbo-technology-pct-technology-technical-article.html

Signed-off-by: louie-tsai <louie.tsai@intel.com>
Added a frequency diagram for Xeon 6776P with PCT on and updated the PCT validation instructions.
@louie-tsai

Copy link
Copy Markdown
Author

@rsiyer-intel
please help to review the PR. thanks

@rsiyer-intel rsiyer-intel requested a review from adgubrud June 25, 2026 01:10
✅ CLOS0 CPU count exactly matches the bucket-0 PCT logical budget.
```

## 4. Benchmark CLOS0 CPUs with Host PerfSpect

@rsiyer-intel rsiyer-intel Jun 25, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please provide link to PerfSpect, users may not be aware of this tool https://github.com/intel/PerfSpect
When you say Host PerfSpect, please clarify it as "Benchmark CLOS0 CPUs with PerfSpect tool on the host" (there is no separate Host and Container PerfSpect)

docker compose --progress=plain --profile set up --abort-on-container-exit
docker compose --progress=plain --profile check up --abort-on-container-exit

./run_host_perfspect_benchmark.sh

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please make this a link to the script.

This is the frequency diagram on Xeon 6776P with PCT on.
<img width="835" height="483" alt="image" src="https://github.com/user-attachments/assets/96f8855c-4b83-4c62-a0dd-fa2408f979fb" />

This is the expected pattern: small active core counts hold the highest PCT turbo

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please clarify that the frequency reported is the frequency when "X" number of cores are active. Can you elaborate what the user needs to understand from above image? Should they be looking at 1-8 cores being active? Are you referring to the SSE frequencies ? They should be ignoring SSE(expected) row.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Frequency steps down as more cores are active, because the average of all the cores is taken ? CLOS0 cores will always operate at higher frequency, no matter how many cores are active?


## Overview

**Intel® Priority Core Turbo (PCT)** is part of **Intel® Speed Select Technology – Turbo Frequency (SST-TF)**.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you have any public links to Intel Speed Select Technology, please add it here.


### PCT bucket-count interpretation

`intel-speed-select turbo-freq info -l <level>` may print the same `bucket-0`,

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you share how user can download or get the intel-speed-select tool ? I dont think it is covered prior to this.
And show a sample output of info -l ?

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see that intel-speed-select is part of the Dockerfile. We should probably have this section after the build section and after tool is introduced.

PCT_TOTAL_LOGICAL_CPUS=32
```

But the `turbo-freq` output shows two reporting anchors per package:

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will be good to specify that this is a 2S 64c per socket - Intel Xeon 6776P system.

Export the kernel build variables first:

```bash
source ./set_kernel_env.sh

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you mention minimum kernel requirement in the main README itself ?
echo "WARN: validated GNR PCT flow expects KERNEL_MM=6.8 and KERNEL_TAG=v6.8." >&2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants