Multiple GPTQ parameter permutations are provided; see Provided Files below for details of the options provided, their parameters, and the software used to create them.
## Task
Generate a SQL query to answer the following question:
`{prompt}`
### Database Schema
This query will run on a database whose schema is represented in this string:
CREATE TABLE products (
product_id INTEGER PRIMARY KEY, -- Unique ID for each product
name VARCHAR(50), -- Name of the product
price DECIMAL(10,2), -- Price of each unit of the product
quantity INTEGER -- Current quantity in stock
);
CREATE TABLE sales (
sale_id INTEGER PRIMARY KEY, -- Unique ID for each sale
product_id INTEGER, -- ID of product sold
customer_id INTEGER, -- ID of customer who made purchase
salesperson_id INTEGER, -- ID of salesperson who made the sale
sale_date DATE, -- Date the sale occurred
quantity INTEGER -- Quantity of product sold
);
-- sales.product_id can be joined with products.product_id
### SQL
Given the database schema, here is the SQL query that answers `{prompt}`:
```sql
Provided files, and GPTQ parameters
Multiple quantisation parameters are provided, to allow you to choose the best one for your hardware and requirements.
Each separate quant is in a different branch. See below for instructions on fetching from different branches.
Most GPTQ files are made with AutoGPTQ. Mistral models are currently made with Transformers.
Explanation of GPTQ parameters
Bits: The bit size of the quantised model.
GS: GPTQ group size. Higher numbers use less VRAM, but have lower quantisation accuracy. "None" is the lowest possible value.
Act Order: True or False. Also known as desc_act. True results in better quantisation accuracy. Some GPTQ clients have had issues with models that use Act Order plus Group Size, but this is generally resolved now.
Damp %: A GPTQ parameter that affects how samples are processed for quantisation. 0.01 is default, but 0.1 results in slightly better accuracy.
GPTQ dataset: The calibration dataset used during quantisation. Using a dataset more appropriate to the model's training can improve quantisation accuracy. Note that the GPTQ calibration dataset is not the same as the dataset used to train the model - please refer to the original model repo for details of the training dataset(s).
Sequence Length: The length of the dataset sequences used for quantisation. Ideally this is the same as the model sequence length. For some very long sequence models (16+K), a lower sequence length may have to be used. Note that a lower sequence length does not limit the sequence length of the quantised model. It only impacts the quantisation accuracy on longer inference sequences.
ExLlama Compatibility: Whether this file can be loaded with ExLlama, which currently only supports Llama models in 4-bit.
If you remove the --local-dir-use-symlinks False parameter, the files will instead be stored in the central Huggingface cache directory (default location on Linux is: ~/.cache/huggingface), and symlinks will be added to the specified --local-dir, pointing to their real location in the cache. This allows for interrupted downloads to be resumed, and allows you to quickly clone the repo to multiple places on disk without triggering a download again. The downside, and the reason why I don't list that as the default option, is that the files are then hidden away in a cache folder and it's harder to know where your disk space is being used, and to clear it up if/when you want to remove a download model.
The cache location can be changed with the HF_HOME environment variable, and/or the --cache-dir parameter to huggingface-cli.
Note that using Git with HF repos is strongly discouraged. It will be much slower than using huggingface-hub, and will use twice as much disk space as it has to store the model files twice (it stores every byte both in the intended target folder, and again in the .git folder as a blob.)
Example Python code for interfacing with TGI (requires huggingface-hub 0.17.0 or later):
pip3 install huggingface-hub
python
1from huggingface_hub import InferenceClient
23endpoint_url ="https://your-endpoint-url-here"45prompt ="Tell me about AI"6prompt_template=f'''## Task
7Generate a SQL query to answer the following question:
8`{prompt}`
910### Database Schema
11This query will run on a database whose schema is represented in this string:
12CREATE TABLE products (
13 product_id INTEGER PRIMARY KEY, -- Unique ID for each product
14 name VARCHAR(50), -- Name of the product
15 price DECIMAL(10,2), -- Price of each unit of the product
16 quantity INTEGER -- Current quantity in stock
17);
1819CREATE TABLE sales (
20 sale_id INTEGER PRIMARY KEY, -- Unique ID for each sale
21 product_id INTEGER, -- ID of product sold
22 customer_id INTEGER, -- ID of customer who made purchase
23 salesperson_id INTEGER, -- ID of salesperson who made the sale
24 sale_date DATE, -- Date the sale occurred
25 quantity INTEGER -- Quantity of product sold
26);
2728-- sales.product_id can be joined with products.product_id
2930### SQL
31Given the database schema, here is the SQL query that answers `{prompt}`:
32```sql
33'''3435client = InferenceClient(endpoint_url)36response = client.text_generation(prompt,37 max_new_tokens=128,38 do_sample=True,39 temperature=0.7,40 top_p=0.95,41 top_k=40,42 repetition_penalty=1.1)4344print(f"Model output: {response}")
How to use this GPTQ model from Python code
Install the necessary packages
Requires: Transformers 4.33.0 or later, Optimum 1.12.0 or later, and AutoGPTQ 0.4.2 or later.
shell
1pip3 install transformers optimum
2pip3 install auto-gptq --extra-index-url https://huggingface.github.io/autogptq-index/whl/cu118/ # Use cu117 if on CUDA 11.7
If you have problems installing AutoGPTQ using the pre-built wheels, install it from source instead:
1from transformers import AutoModelForCausalLM, AutoTokenizer, pipeline
23model_name_or_path ="TheBloke/sqlcoder2-GPTQ"4# To use a different branch, change revision5# For example: revision="gptq-4bit-32g-actorder_True"6model = AutoModelForCausalLM.from_pretrained(model_name_or_path,7 device_map="auto",8 trust_remote_code=False,9 revision="main")1011tokenizer = AutoTokenizer.from_pretrained(model_name_or_path, use_fast=True)1213prompt ="Tell me about AI"14prompt_template=f'''## Task
15Generate a SQL query to answer the following question:
16`{prompt}`
1718### Database Schema
19This query will run on a database whose schema is represented in this string:
20CREATE TABLE products (
21 product_id INTEGER PRIMARY KEY, -- Unique ID for each product
22 name VARCHAR(50), -- Name of the product
23 price DECIMAL(10,2), -- Price of each unit of the product
24 quantity INTEGER -- Current quantity in stock
25);
2627CREATE TABLE sales (
28 sale_id INTEGER PRIMARY KEY, -- Unique ID for each sale
29 product_id INTEGER, -- ID of product sold
30 customer_id INTEGER, -- ID of customer who made purchase
31 salesperson_id INTEGER, -- ID of salesperson who made the sale
32 sale_date DATE, -- Date the sale occurred
33 quantity INTEGER -- Quantity of product sold
34);
3536-- sales.product_id can be joined with products.product_id
3738### SQL
39Given the database schema, here is the SQL query that answers `{prompt}`:
40```sql
41'''4243print("\n\n*** Generate:")4445input_ids = tokenizer(prompt_template, return_tensors='pt').input_ids.cuda()46output = model.generate(inputs=input_ids, temperature=0.7, do_sample=True, top_p=0.95, top_k=40, max_new_tokens=512)47print(tokenizer.decode(output[0]))4849# Inference can also be done using transformers' pipeline5051print("*** Pipeline:")52pipe = pipeline(53"text-generation",54 model=model,55 tokenizer=tokenizer,56 max_new_tokens=512,57 do_sample=True,58 temperature=0.7,59 top_p=0.95,60 top_k=40,61 repetition_penalty=1.162)6364print(pipe(prompt_template)[0]['generated_text'])
Compatibility
The files provided are tested to work with AutoGPTQ, both via Transformers and using AutoGPTQ directly. They should also work with Occ4m's GPTQ-for-LLaMa fork.
ExLlama is compatible with Llama and Mistral models in 4-bit. Please see the Provided Files table above for per-file compatibility.
I've had a lot of people ask if they can contribute. I enjoy providing models and helping people, and would love to be able to spend even more time doing it, as well as expanding into new projects like fine tuning/training.
If you're able and willing to contribute it will be most gratefully received and will help me to keep providing more models, and to start work on new AI projects.
Donaters will get priority support on any and all AI/LLM/model questions and requests, access to a private Discord room, plus other benefits.
Patreon special mentions: Pierre Kircher, Stanislav Ovsiannikov, Michael Levine, Eugene Pentland, Andrey, 준교 김, Randy H, Fred von Graf, Artur Olbinski, Caitlyn Gatomon, terasurfer, Jeff Scroggin, James Bentley, Vadim, Gabriel Puliatti, Harry Royden McLaughlin, Sean Connelly, Dan Guido, Edmond Seymore, Alicia Loh, subjectnull, AzureBlack, Manuel Alberto Morcote, Thomas Belote, Lone Striker, Chris Smitley, Vitor Caleffi, Johann-Peter Hartmann, Clay Pascal, biorpg, Brandon Frisco, sidney chen, transmissions 11, Pedro Madruga, jinyuan sun, Ajan Kanaga, Emad Mostaque, Trenton Dambrowitz, Jonathan Leane, Iucharbius, usrbinkat, vamX, George Stoitzev, Luke Pendergrass, theTransient, Olakabola, Swaroop Kallakuri, Cap'n Zoog, Brandon Phillips, Michael Dempsey, Nikolai Manek, danny, Matthew Berman, Gabriel Tamborski, alfie_i, Raymond Fosdick, Tom X Nguyen, Raven Klaugh, LangChain4j, Magnesian, Illia Dulskyi, David Ziegler, Mano Prime, Luis Javier Navarrete Lozano, Erik Bjäreholt, 阿明, Nathan Dryer, Alex, Rainer Wilmers, zynix, TL, Joseph William Delisle, John Villwock, Nathan LeClaire, Willem Michiel, Joguhyik, GodLy, OG, Alps Aficionado, Jeffrey Morgan, ReadyPlayerEmma, Tiffany J. Kim, Sebastain Graf, Spencer Kim, Michael Davis, webtim, Talal Aujan, knownsqashed, John Detwiler, Imad Khwaja, Deo Leter, Jerry Meng, Elijah Stavena, Rooh Singh, Pieter, SuperWojo, Alexandros Triantafyllidis, Stephen Murray, Ai Maven, ya boyyy, Enrico Ros, Ken Nordquist, Deep Realms, Nicholas, Spiking Neurons AB, Elle, Will Dee, Jack West, RoA, Luke @flexchar, Viktor Bowallius, Derek Yates, Subspace Studios, jjj, Toran Billups, Asp the Wyvern, Fen Risland, Ilya, NimbleBox.ai, Chadd, Nitin Borwankar, Emre, Mandus, Leonard Tan, Kalila, K, Trailburnt, S_X, Cory Kujawski
Thank you to all my generous patrons and donaters!
And thank you again to a16z for their generous grant.
Original model card: Defog.ai's Sqlcoder2
Defog SQLCoder
Defog's SQLCoder is a state-of-the-art LLM for converting natural language questions to SQL queries.
SQLCoder is a 15B parameter model that outperforms gpt-3.5-turbo for natural language to SQL generation tasks on our sql-eval framework, and significantly outperforms all popular open-source models. When fine-tuned on a given schema, it also outperforms gpt-4
SQLCoder is fine-tuned on a base StarCoder model.
Results on novel datasets not seen in training
model
perc_correct
gpt4-2023-10-04
82.0
defog-sqlcoder2
74.5
gpt4-2023-08-28
74.0
defog-sqlcoder-7b
71.0
gpt-3.5-2023-10-04
66.0
claude-2
64.5
gpt-3.5-2023-08-28
61.0
claude_instant_1
61.0
text-davinci-003
52.5
License
The code in this repo (what little there is of it) is Apache-2 licensed. The model weights have a CC BY-SA 4.0 license, with additional responsible use restrictions added. The TL;DR is that you can use and modify the model for any purpose – including commercial use. However, if you modify the weights (for example, by fine-tuning), you must open-source your modified weights under the same license terms.
Training
Defog was trained on more than 20,000 human-curated questions. These questions were based on 10 different schemas. None of the schemas in the training data were included in our evaluation framework.
We classified each generated question into one of 5 categories. The table displays the percentage of questions answered correctly by each model, broken down by category.
query_category
gpt-4
sqlcoder2-15b
sqlcoder-7b
gpt-3.5
claude-2
claude-instant
gpt-3
date
72
76
64
68
52
48
32
group_by
91.4
80
82.9
77.1
71.4
71.4
71.4
order_by
82.9
77.1
74.3
68.6
74.3
74.3
68.6
ratio
80
60
54.3
37.1
57.1
45.7
25.7
join
82.9
77.1
74.3
71.4
65.7
62.9
57.1
where
80
77.1
74.3
74.3
62.9
60
54.3
Using SQLCoder
You can use SQLCoder via the transformers library by downloading our model weights from the Hugging Face repo. We have added sample code for inference on a sample database schema.
bash
1python inference.py -q "Question about the sample database goes here"23# Sample question:4# Do we get more revenue from customers in New York compared to customers in San Francisco? Give me the total revenue for each city, and the difference between the two.
You can also use a demo on our website here, or run SQLCoder in Colab here
Hardware Requirements
SQLCoder has been tested on an A100 40GB GPU with bfloat16 weights. You can also load an 8-bit and 4-bit quantized version of the model on consumer GPUs with 20GB or more of memory – like RTX 4090, RTX 3090, and Apple M2 Pro, M2 Max, or M2 Ultra Chips with 20GB or more of memory.
Todo
Open-source the v1 model weights
Train the model on more data, with higher data variance
Tune the model further with Reward Modelling and RLHF
Pretrain a model from scratch that specializes in SQL analysis