update xpu docker image and use public ipex whel #1860
Conversation
Signed-off-by: Wang, Yi A <yi.a.wang@intel.com>
|
@Narsil @OlivierDehaene @mfuntowicz @yao-matrix please have review |
|
Why is the size of a CPU image (sha-ac7076b-intel) approximately 47.3 GB? |
|
with the PR, the docker image is dropped to 26.5GB |
|
Another question, is it normal that the speed on CPU (Xeon(R) Gold 6442Y) is 20 times slower than on GPU (A6000) currently? |
Could you elaborate the benchmark case? Like you use which script and what configurations? From FLOPS performance, 6442Y has AMX and 24 cores（which means it's a middle end CPU, spec is here）, one 6442Y socket BF16 TFLOPS is ~1/3 of A6000(spec is here). So more details on benchmark is needed to verify if your 1/20 is reasonable. |
|
Just did a simple test with the same prompt (outputting around 100 tokens) using a rough calculation method on tgi api (using api docs). A6000 took ~2 seconds while 6442Y needed ~40 seconds. Do you have any benchmark results using CPU image that can be shared? |
# What does this PR do? <!-- Congratulations! You've made it this far! You're not quite done yet though. Once merged, your PR is going to appear in the release notes with the title you set, so make sure it's a great title that fully reflects the extent of your awesome contribution. Then, please replace this with a description of the change and which issue is fixed (if applicable). Please also include relevant motivation and context. List any dependencies (if any) that are required for this change. Once you're done, someone will review your PR shortly (see the section "Who can review?" below to tag some potential reviewers). They may suggest changes to make the code even better. If no one reviewed your PR after a week has passed, don't hesitate to post a new comment @-mentioning the same persons---sometimes notifications get lost. --> <!-- Remove if not applicable --> Fixes # (issue) ## Before submitting - [ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case). - [ ] Did you read the [contributor guideline](https://github.com/huggingface/transformers/blob/main/CONTRIBUTING.md#start-contributing-pull-requests), Pull Request section? - [ ] Was this discussed/approved via a Github issue or the [forum](https://discuss.huggingface.co/)? Please add a link to it if that's the case. - [ ] Did you make sure to update the documentation with your changes? Here are the [documentation guidelines](https://github.com/huggingface/transformers/tree/main/docs), and [here are tips on formatting docstrings](https://github.com/huggingface/transformers/tree/main/docs#writing-source-documentation). - [ ] Did you write any new necessary tests? ## Who can review? Anyone in the community is free to review the PR once the tests have passed. Feel free to tag members/contributors who may be interested in your PR. <!-- Your PR will be replied to more quickly if you can figure out the right person to tag with @ @OlivierDehaene OR @Narsil --> Signed-off-by: Wang, Yi A <yi.a.wang@intel.com>
What does this PR do?
Fixes # (issue)
Before submitting
Pull Request section?
to it if that's the case.
documentation guidelines, and
here are tips on formatting docstrings.
Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.