Skip to content

Commit

Permalink
docs: add more videos to docs (GITBOOK-787)
Browse files Browse the repository at this point in the history
  • Loading branch information
mikeldking authored and gitbook-bot committed Aug 3, 2024
1 parent 2772397 commit cb9ee71
Show file tree
Hide file tree
Showing 2 changed files with 9 additions and 1 deletion.
8 changes: 7 additions & 1 deletion docs/datasets-and-experiments/use-cases-datasets/text2sql.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,8 @@

[![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/arize-ai/phoenix/blob/main/tutorials/experiments/txt2sql.ipynb)

{% embed url="https://www.youtube.com/watch?v=rzxN-YV_DbE" %}

Let's work through a Text2SQL use case where we are starting from scratch without a nice and clean dataset of questions, SQL queries, or expected responses.

```shell
Expand Down Expand Up @@ -395,7 +397,11 @@ experiment = run_experiment(

Interesting! It looks like the smaller model is able to do decently well but we might want to ensure it follows instructions as well as a larger model. We can actually grab all the LLM spans from our previous GPT40 runs and use them to generate a OpenAI fine-tuning JSONL file!

![](https://storage.googleapis.com/arize-assets/phoenix/assets/images/fine\_tining\_nba.png) ![](https://storage.googleapis.com/arize-assets/phoenix/assets/images/openai\_ft.png)
 

<figure><img src="https://storage.googleapis.com/arize-assets/phoenix/assets/images/openai_ft.png" alt=""><figcaption></figcaption></figure>

<figure><img src="https://storage.googleapis.com/arize-assets/phoenix/assets/images/fine_tining_nba.png" alt=""><figcaption></figcaption></figure>

### Conclusion

Expand Down
2 changes: 2 additions & 0 deletions docs/deployment/persistence.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,3 +17,5 @@ By default Phoenix uses SQLite so that it runs with no external dependancies. Th
## PostgreSQL

Phoenix also can natively be backed by PostgreSQL. To make Phoenix talk to PostgreSQL instead of SQLite, you will have to set the **PHOENIX\_SQL\_DATABASE\_URL** to your PostgreSQL instance.

{% embed url="https://www.youtube.com/watch?v=9hNrosMqirQ" %}

0 comments on commit cb9ee71

Please sign in to comment.