> For the complete documentation index, see [llms.txt](https://dgpt.gitbook.io/dgpt-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dgpt.gitbook.io/dgpt-docs/project-background/ai-server-evolution-and-parallelism.md).

# AI Server Evolution and Parallelism

Servers have gone through an evolution of four models with scenario requirements: general purpose servers, cloud servers, edge servers, and AI servers.AI servers have enhanced their parallel computing capabilities by adopting GPUs to better support the needs of AI applications;&#x20;

AI servers can be divided into two types, training and inference, based on application scenarios. The training process requires high chip arithmetic, and according to IDC, the proportion of inference arithmetic demand is expected to rise to 60.8% by 2025, with the widespread application of large models;

AI servers can be divided into CPU+GPU, CPU+FPGA, CPU+ASIC and other forms of combination according to the type of chip. At present, the main choice in China is the CPU+GPU combination, accounting for 91.9%;

The cost of AI servers comes mainly from chips such as CPUs and GPUs, which take up anywhere from 25 to 70 per cent of the total cost. For training servers, more than 80 per cent of the cost comes from the CPU and GPU.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://dgpt.gitbook.io/dgpt-docs/project-background/ai-server-evolution-and-parallelism.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
