ai-agent-book 精选快照(<2MB 代码与文档,来自 github.com/bojieli/ai-agent-book)
Build latest book artifacts / build (push) Canceled after 0s
dependency resolution / resolve (3.11) (push) Canceled after 0s
dependency resolution / resolve (3.13) (push) Canceled after 0s
deploy-pages / build (push) Canceled after 0s
deploy-pages / deploy (push) Canceled after 0s
i18n consistency check / check (push) Canceled after 0s
provider adoption tests / test (chapter2/context-compression) (push) Canceled after 0s
provider adoption tests / test (chapter2/prompt-injection) (push) Canceled after 0s
provider adoption tests / test (chapter2/system-hint) (push) Canceled after 0s
provider adoption tests / test (chapter3/log-sanitization) (push) Canceled after 0s
web-search-agent tests / test (push) Canceled after 0s
web-search-agent tests / agentbook (push) Canceled after 0s
Build latest book artifacts / build (push) Canceled after 0s
dependency resolution / resolve (3.11) (push) Canceled after 0s
dependency resolution / resolve (3.13) (push) Canceled after 0s
deploy-pages / build (push) Canceled after 0s
deploy-pages / deploy (push) Canceled after 0s
i18n consistency check / check (push) Canceled after 0s
provider adoption tests / test (chapter2/context-compression) (push) Canceled after 0s
provider adoption tests / test (chapter2/prompt-injection) (push) Canceled after 0s
provider adoption tests / test (chapter2/system-hint) (push) Canceled after 0s
provider adoption tests / test (chapter3/log-sanitization) (push) Canceled after 0s
web-search-agent tests / test (push) Canceled after 0s
web-search-agent tests / agentbook (push) Canceled after 0s
This commit is contained in:
@@ -0,0 +1,27 @@
|
||||
# Chapter 4: Fine-tuning and Deployment
|
||||
|
||||
A general model rarely fits a specific product out of the box. The usual fix is
|
||||
**fine-tuning**: continuing to train the model on a smaller, task-specific
|
||||
dataset so it adapts to your domain while keeping its general ability.
|
||||
|
||||
Fine-tuning changes how the model turns a **prompt** into an answer, but it does
|
||||
not change the basic pipeline: text becomes a **token**, each token becomes an
|
||||
**embedding**, and **inference** produces the result. What changes is the
|
||||
weights the model learned.
|
||||
|
||||
```python
|
||||
def fine_tune(model, dataset):
|
||||
for prompt, target in dataset:
|
||||
loss = model.loss(prompt, target) # compare output to target
|
||||
model.update(loss) # adjust weights
|
||||
return model
|
||||
```
|
||||
|
||||
After fine-tuning comes **deployment**: packaging the model behind an API so real
|
||||
users can send a prompt and get an answer. Here the earlier concerns return with
|
||||
full force. Latency must stay low, throughput must stay high, and the KV cache
|
||||
and batching from the previous chapter do the heavy lifting.
|
||||
|
||||
The full journey — token, embedding, prompt, inference, latency, fine-tuning,
|
||||
and deployment — is now complete. A model that was once a research artifact has
|
||||
become a service that people can actually use.
|
||||
Reference in New Issue
Block a user