Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add contexual embedding algorithm notebook #311

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

IANTHEREAL
Copy link
Contributor

@IANTHEREAL IANTHEREAL commented Sep 28, 2024

doc:https://docs.pingcap.com/tidb/v7.5/tiup-component-management
model: claude-3-haiku-20240307(use prompt caching)
guide: https://github.com/anthropics/anthropic-cookbook/blob/main/skills/contextual-embeddings/guide.ipynb

Cost(chunk 1 be processed twice, so the total cost = cost_of_chunk1 * 2 + cost_of_chunk2):
image

Effect Comparison for chunk 1

contexual embedding

This chunk provides an overview of the various TiUP commands that can be used to manage TiUP components, including commands for querying, installing, upgrading, and uninstalling components.

Token usage:
DEBUG:root:Input tokens: 346
DEBUG:root:Output tokens: 45
DEBUG:root:Cache creation input tokens: 2544
DEBUG:root:Cache read input tokens: 0

Llama index metadata

## Summary:

This section focuses on **managing TiUP components** using various **TiUP commands**. 

**Key topics:**

* **Component management operations:** Installing, updating, uninstalling, checking status, cleaning up, and linking/unlinking components.
* **TiUP commands:** `list`, `install`, `update`, `uninstall`, `status`, `clean`, `help`, `link`, `unlink`.

**Key entities:**

* **TiUP components:**  Software components within the TiUP ecosystem, such as TiDB, TiKV, TiSpark, etc.
* **TiUP commands:**  Commands used to interact with and manage TiUP components.

Effect Comparison for chunk 2

contexual embedding

This chunk describes how to upgrade TiUP components using the `tiup update` command, including upgrading all components to the latest versions, upgrading to the nightly version, and upgrading TiUP itself.

Token usage:
DEBUG:root:Input tokens: 300
DEBUG:root:Output tokens: 50
DEBUG:root:Cache creation input tokens: 0
DEBUG:root:Cache read input tokens: 2544

Llama index metadata

## Summary:

This section focuses on **upgrading TiDB components** using the `tiup update` command. It explains the command's usage and highlights key flags:

**Key Topics:**

* **Component Upgrade:**  How to update TiDB components to newer versions.
* **`tiup update` Command:**  The command used for upgrading components.
* **Flags:**  Various flags available with the `tiup update` command, including:
    * `--all`: Upgrades all components.
    * `--nightly`: Upgrades to the nightly version.
    * `--self`: Upgrades TiUP itself.
    * `--force`: Forcibly upgrades to the latest version.

**Key Entities:**

* **TiUP:** The command-line tool used for managing TiDB clusters.
* **Components:**  Individual parts of a TiDB cluster, such as TiDB, TiKV, and TiSpark.
* **Nightly Version:**  A pre-release version of a component.

**Overall, the section provides a concise guide on how to upgrade TiDB components using the `tiup update` command, emphasizing the available flags and their functionalities.**

Copy link

vercel bot commented Sep 28, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
tidb-ai-preview ✅ Ready (Inspect) Visit Preview 💬 Add feedback Sep 28, 2024 8:04am
tidb-ai-storybook ✅ Ready (Inspect) Visit Preview 💬 Add feedback Sep 28, 2024 8:04am

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant