Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for Intel GPUs (Such as A770) #2436

Open
utkuoguzman opened this issue Jan 9, 2025 · 3 comments
Open

Support for Intel GPUs (Such as A770) #2436

utkuoguzman opened this issue Jan 9, 2025 · 3 comments
Labels
AEP Arbor Enhancement Proposal enhancement

Comments

@utkuoguzman
Copy link

utkuoguzman commented Jan 9, 2025

Hardware Support for Intel GPUs

Goal

Arbor should support for the Intel GPUs because Arbor uses floating-point 64 as the main precision and Intel GPUs currently have the best performance per price when it comes to FP64 computations.

Rationale

Because unlike Nvidia who uses a 1:64 downgraded FP64 performance or AMD who uses a 1:32 downgrade, Intel actually uses 1:8 downgrade. Meaning Intel Arc A770 has the theoretical computation power of 2.458 TFLOPS at FP64, at the price point of 329$ right now. (https://www.techpowerup.com/gpu-specs/arc-a770.c3914)
Considering the fact that many "FP64" GPUs are professional grade (aka "pricey"), and many of the cheap ones aren't produced since forever, supporting Intel GPUs will be supporting the community.
And considering the fact that Intel B580 goes the same route by providing 1:8 downgrade, it would be a long-term benefit.

Scope

Just like ROCm and Cuda, give an experimental support for Intel for every feature. Probably through OpenCL or OneAPI.

Implementation

That is a too advanced topic for me, but since you give support for ROCm, it would probably be no problem for you, may be a fun small-scale challenge even.

@utkuoguzman utkuoguzman added AEP Arbor Enhancement Proposal enhancement labels Jan 9, 2025
@thorstenhater
Copy link
Contributor

Hi @utkuoguzman,

we have discussed this topic on and off for a long time. For now, nobody in our team has access
to these cards and the current / upcoming generation of the HPC machines we work with deploy
NVIDIA GPUs. Thus, until that situation changes, this is on our agenda, but not a priority. And without
stable access to the proper hardware, we cannot really start work on it.

@utkuoguzman
Copy link
Author

Okay, very understandable.
My other sane option was AMD, but you said you'll mainly use NVIDIA GPUs. So should I have to know some important detail when it comes to using ARBOR's experimental ROCm support? Or should I just go all NVIDA?
Thanks.

@thorstenhater
Copy link
Contributor

Yes, for now NVIDIA is the backend that is most used and supported. As you might gather from our profiles, most of us work at HPC centres and as such, we follow their procurement trends. That doesn't mean alternatives fall to the wayside, but it guides our focus.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AEP Arbor Enhancement Proposal enhancement
Projects
None yet
Development

No branches or pull requests

2 participants