# Ray Feature Support

**URL:** <https://discuss.ray.io/t/ray-feature-support/23510>\
**Category:** Uncategorized\
**Created:** [March 26, 2026, 4:18am UTC](https://discuss.ray.io/t/ray-feature-support/23510 "2026-03-26T04:18:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![yifeng-x](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/yifeng-x/32/8487_2.png) [@yifeng-x](https://discuss.ray.io/u/yifeng-x)\
**Post date:** [March 26, 2026, 4:18am UTC](https://discuss.ray.io/t/ray-feature-support/23510/1 "2026-03-26T04:18:30Z")

</div>

Is Ray related to hardware resources? If so, how well does it support domestic AI accelerators such as **Ascend** and **Muxi** , and does it provide **full Ray capabilities** for these chips?

---

<div class="post-metadata">

**Author:** ![RunLLM](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/runllm/32/8249_2.png) [@RunLLM](https://discuss.ray.io/u/RunLLM)\
**Post date:** [March 26, 2026, 4:18am UTC](https://discuss.ray.io/t/ray-feature-support/23510/2 "2026-03-26T04:18:56Z")

</div>

Yes, Ray is closely related to hardware resources—it provides native support for scheduling and isolating tasks and actors on various accelerators, including CPUs, GPUs, and other AI chips. Ray allows you to specify resource requirements (like CPUs, GPUs, or custom accelerators) for each task or actor, and manages resource allocation and isolation automatically. This enables efficient use of heterogeneous hardware in distributed ML and Python applications. See [Accelerator Support](https://github.com/ray-project/ray/blob/master/doc/source/ray-core/scheduling/accelerators.rst) and [Ray Accelerator Support REP](https://github.com/ray-project/enhancements/blob/main/reps/2023-10-13-accelerator-support.md).

For domestic AI accelerators such as Huawei Ascend (NPU), Ray provides experimental support. You can schedule tasks and actors using the “NPU” resource, and Ray will set the appropriate environment variables (e.g., `ASCEND_RT_VISIBLE_DEVICES`) for device isolation. However, this support is marked as experimental and not fully tested by the Ray team; some advanced Ray features may not be as robust as on NVIDIA GPUs. There is no official mention of Muxi accelerator support in the provided data sources, so its support status is unclear. See [Accelerator Support Table](https://github.com/ray-project/ray/blob/master/doc/source/ray-core/scheduling/accelerators.rst) and [NPU AcceleratorManager](https://github.com/ray-project/ray/blob/master/python/ray/_private/accelerators/npu.py).

Would you like more detail on how to use Ray with Ascend NPUs or on the current limitations?

Sources:

- [Accelerator Support](https://github.com/ray-project/ray/blob/master/doc/source/ray-core/scheduling/accelerators.rst)
- [Ray Accelerator Support REP](https://github.com/ray-project/enhancements/blob/main/reps/2023-10-13-accelerator-support.md)
- [NPU AcceleratorManager](https://github.com/ray-project/ray/blob/master/python/ray/_private/accelerators/npu.py)

Hint: Mention @RunLLM in the post for followups.