[NPU] [DOC] Fix outdated descriptions in the NPU documentation (#22707)
This commit is contained in:
@@ -73,7 +73,7 @@ Also, do not rely on the "Latency/Output throughput" from this script, as it is
|
|||||||
GSM8K is too easy for state-of-the-art models nowadays. Please try your own more challenging accuracy tests.
|
GSM8K is too easy for state-of-the-art models nowadays. Please try your own more challenging accuracy tests.
|
||||||
You can find additional accuracy eval examples in:
|
You can find additional accuracy eval examples in:
|
||||||
- [test_eval_accuracy_large.py](https://github.com/sgl-project/sglang/blob/main/test/registered/eval/test_eval_accuracy_large.py)
|
- [test_eval_accuracy_large.py](https://github.com/sgl-project/sglang/blob/main/test/registered/eval/test_eval_accuracy_large.py)
|
||||||
- [test_moe_eval_accuracy_large.py](https://github.com/sgl-project/sglang/blob/main/test/registered/eval/test_moe_eval_accuracy_large.py)
|
- [test_gpt_oss_1gpu.py](https://github.com/sgl-project/sglang/blob/main/test/registered/core/test_gpt_oss_1gpu.py)
|
||||||
|
|
||||||
## Benchmark the speed
|
## Benchmark the speed
|
||||||
Refer to [Benchmark and Profiling](../../developer_guide/benchmark_and_profiling.md).
|
Refer to [Benchmark and Profiling](../../developer_guide/benchmark_and_profiling.md).
|
||||||
@@ -113,7 +113,7 @@ Each CI workflow has a default limit defined in its workflow configuration file.
|
|||||||
|
|
||||||
```yaml
|
```yaml
|
||||||
cool-down-minutes:
|
cool-down-minutes:
|
||||||
description: "Default cooldown period in minutes; 0 disables rate limiting"
|
description: "Cooldown period in minutes for low-permission users; 0 disables rate limiting"
|
||||||
type: number
|
type: number
|
||||||
default: 120
|
default: 120
|
||||||
```
|
```
|
||||||
@@ -133,7 +133,7 @@ Users listed in [CI_PERMISSIONS.json](https://github.com/sgl-project/sglang/blob
|
|||||||
- Reuse server launches in your unit tests to make tests run faster.
|
- Reuse server launches in your unit tests to make tests run faster.
|
||||||
- When supporting new hardware or features, follow these guidelines:
|
- When supporting new hardware or features, follow these guidelines:
|
||||||
- Do not drastically change existing code.
|
- Do not drastically change existing code.
|
||||||
- Always prefer new files to introduce specific components for your new hardware (e.g., `allocator_ascend.py`).
|
- Always prefer new files to introduce specific components for your new hardware (e.g., `allocator_npu.py`).
|
||||||
- If you write multiple if/else blocks for new features, ensure the common path (e.g., NVIDIA hardware or the existing code path) is the first branch.
|
- If you write multiple if/else blocks for new features, ensure the common path (e.g., NVIDIA hardware or the existing code path) is the first branch.
|
||||||
|
|
||||||
## How to update sgl-kernel
|
## How to update sgl-kernel
|
||||||
|
|||||||
Reference in New Issue
Block a user