LLM Apps in Production (RAG + Vector DB + Caching) · 课时

监控成本与延迟

设置工具和实践来跟踪 LLM 应用程序接口成本及应用延迟，从而持续优化。

监控成本与延迟 是 CoddyKit 上的免费 LLM Apps in Production (RAG + Vector DB + Caching) 课时。这是第 3 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 LLM Apps in Production (RAG + Vector DB + Caching) 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 LLM Apps in Production (RAG + Vector DB + Caching) 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

Crucial for LLM App Health

Deploying Large Language Model (LLM) applications to production comes with unique challenges. Two critical aspects to continuously monitor are operational costs and application latency.

Monitoring helps you ensure your LLM app runs smoothly, efficiently, and within budget, delivering a great user experience.

Understanding LLM API Costs

Most LLM providers charge based on token usage. A token is a piece of a word, like 'hel' or 'lo'. You typically pay for:

Input Tokens: The text you send to the LLM (your prompt and context).
Output Tokens: The text the LLM generates as its response.

Prices vary by model and token type, so tracking usage is key to managing expenses.

Provider Dashboards for Costs

The simplest way to start tracking LLM costs is by using the dashboards provided by your LLM API vendor (e.g., OpenAI, Anthropic). These dashboards usually offer:

An overview of your total spending.
Breakdowns of usage by specific models.
Historical data and trend analysis.

They provide a convenient, high-level view of your expenditure.

Programmatic Cost Tracking

For more granular control and integration into your own systems, you can log token usage directly from your application. LLM API responses often include detailed token counts. Here's a Python example:

import openai

# This client would be initialized with your API key
# client = openai.OpenAI(api_key="YOUR_OPENAI_API_KEY")

def get_llm_response_with_cost(prompt):
    try:
        # Simulate an LLM call without actual API key setup
        # In a real app, 'client.chat.completions.create(...)' would be used
        response_mock = type('obj', (object,), {
            'choices': [type('obj', (object,), {'message': type('obj', (object,), {'content': 'The capital of France is Paris.'})})],
            'usage': type('obj', (object,), {
                'prompt_tokens': 10,
                'completion_tokens': 5,
                'total_tokens': 15
            })
        })()
        
        usage = response_mock.usage # In real code: response.usage
        print(f"Prompt Tokens: {usage.prompt_tokens}")
        print(f"Completion Tokens: {usage.completion_tokens}")
        print(f"Total Tokens: {usage.total_tokens}")
        return response_mock.choices[0].message.content # In real code: response.choices[0].message.content
    except Exception as e:
        print(f"Error: {e}")
        return "Error generating response."

if __name__ == "__main__":
    print("--- LLM Cost Logging Demo --- ")
    get_llm_response_with_cost("What is the capital of France?")

Understanding Latency in RAG

Latency refers to the delay between sending a request and receiving a response. For a Retrieval Augmented Generation (RAG) application, this isn't just the LLM call; it includes several stages:

Time to retrieve documents from your vector database.
The actual LLM API call duration.
Any preprocessing or postprocessing steps.

High latency can lead to a frustratingly slow user experience.

Measuring Latency in Your App

To optimize your RAG system's performance, you need to identify where delays are occurring. This means measuring the time taken for each critical component of your pipeline:

Data ingestion and chunking.
Embedding generation.
Vector database queries.
LLM API calls.

Python's time module is a simple yet effective tool for this.

Practical Latency Logging

Let's extend our previous example to measure the duration of an LLM call. This is often the most significant contributor to overall RAG latency:

import openai
import time

# This client would be initialized with your API key
# client = openai.OpenAI(api_key="YOUR_OPENAI_API_KEY")

def get_llm_response_timed(prompt):
    start_time = time.time()
    try:
        # Simulate an LLM call without actual API key setup
        # In a real app, 'client.chat.completions.create(...)' would be used
        # Simulate a network delay
        time.sleep(0.5)
        response_mock = type('obj', (object,), {
            'choices': [type('obj', (object,), {'message': type('obj', (object,), {'content': 'Once upon a time, there was a brave knight.'})})],
        })()
        
        end_time = time.time()
        duration = end_time - start_time
        print(f"LLM Call Duration: {duration:.2f} seconds")
        return response_mock.choices[0].message.content # In real code: response.choices[0].message.content
    except Exception as e:
        print(f"Error: {e}")
        return "Error generating response."

if __name__ == "__main__":
    print("--- LLM Latency Logging Demo --- ")
    get_llm_response_timed("Tell me a short story about a brave knight.")

Centralizing Metrics & Tools

For a holistic view of your application's health, it's best to centralize your logs and metrics using dedicated monitoring tools. Popular choices include:

Prometheus: Excellent for collecting and storing time-series data (metrics).
Grafana: For building powerful, customizable dashboards and visualizations.
Datadog / New Relic: All-in-one observability platforms that combine metrics, logs, and traces.

These platforms help you visualize trends and quickly pinpoint issues.

Setting Up Proactive Alerts

While monitoring helps you understand what's happening, alerting ensures you're notified immediately when something goes wrong. Configure alerts to trigger if:

Your monthly LLM API costs exceed a predefined budget.
The average response latency for your RAG system spikes unexpectedly.
Error rates for LLM calls or retrieval increase significantly.

Proactive alerts enable you to address problems before they negatively impact users or your budget.

Quick Check: Monitoring Costs

You've learned about tracking LLM costs and latency. Let's test your understanding of why monitoring token usage is so important.

Recap: Monitor for Success

Monitoring costs and latency is absolutely vital for any production LLM application. By programmatically tracking token usage and timing key operations, you gain crucial insights to optimize your system's performance and manage budgets effectively.

Integrating with observability platforms and setting up proactive alerts ensures your RAG system remains efficient, cost-effective, and provides a reliable user experience.

常见问题解答

「监控成本与延迟」课时是免费的吗？

是的 — 「监控成本与延迟」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 LLM Apps in Production (RAG + Vector DB + Caching) 课程的其余内容，请升级到 CoddyKit PRO。 LLM Apps in Production (RAG + Vector DB + Caching) 课程共包含 4 节课。

「监控成本与延迟」这节课中我会学到什么？

设置工具和实践来跟踪 LLM 应用程序接口成本及应用延迟，从而持续优化。你通过在浏览器中直接运行的动手代码来练习 LLM Apps in Production (RAG + Vector DB + Caching)，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 LLM Apps in Production (RAG + Vector DB + Caching) 需要有经验吗？

无需任何先前经验。CoddyKit 上的 LLM Apps in Production (RAG + Vector DB + Caching) 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 3 节课，共 4 节。

「监控成本与延迟」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 LLM Apps in Production (RAG + Vector DB + Caching) 课中编写并运行代码吗？

能。每节 LLM Apps in Production (RAG + Vector DB + Caching) 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 LLM Apps in Production (RAG + Vector DB + Caching)