This is Gemma 1.1 7B (IT), an update over the original instruction-tuned Gemma release.
Gemma 1.1 was trained using a novel RLHF method, leading to substantial gains on quality, coding capabilities, factuality, instruction following and multi-turn conversation quality. We also fixed a bug in multi-turn conversations, and made sure that model responses don't always start with "Sure,".
We believe this release represents an improvement for most use cases, but we encourage users to test in their particular applications. The previous model will continue to be available in the same repo. We appreciate the enthusiastic adoption of Gemma, and we continue to welcome all feedback from the community.
Summary description and brief definition of inputs and outputs.
Description
Gemma is a family of lightweight, state-of-the-art open models from Google,
built from the same research and technology used to create the Gemini models.
They are text-to-text, decoder-only large language models, available in English,
with open weights, pre-trained variants, and instruction-tuned variants. Gemma
models are well-suited for a variety of text generation tasks, including
question answering, summarization, and reasoning. Their relatively small size
makes it possible to deploy them in environments with limited resources such as
a laptop, desktop or your own cloud infrastructure, democratizing access to
state of the art AI models and helping foster innovation for everyone.
Usage
Below we share some code snippets on how to get quickly started with running the model. First make sure to pip install -U transformers, then copy the snippet from the section that is relevant for your usecase.
Running the model on a CPU
As explained below, we recommend torch.bfloat16 as the default dtype. You can use a different precision if necessary.
python
1from transformers import AutoTokenizer, AutoModelForCausalLM
2import torch
34tokenizer = AutoTokenizer.from_pretrained("google/gemma-1.1-7b-it")5model = AutoModelForCausalLM.from_pretrained(6"google/gemma-1.1-7b-it",7 torch_dtype=torch.bfloat16
8)910input_text ="Write me a poem about Machine Learning."11input_ids = tokenizer(input_text, return_tensors="pt")1213outputs = model.generate(**input_ids, max_new_tokens=50)14print(tokenizer.decode(outputs[0]))
Running the model on a single / multi GPU
python
1# pip install accelerate2from transformers import AutoTokenizer, AutoModelForCausalLM
3import torch
45tokenizer = AutoTokenizer.from_pretrained("google/gemma-1.1-7b-it")6model = AutoModelForCausalLM.from_pretrained(7"google/gemma-1.1-7b-it",8 device_map="auto",9 torch_dtype=torch.bfloat16
10)1112input_text ="Write me a poem about Machine Learning."13input_ids = tokenizer(input_text, return_tensors="pt").to("cuda")1415outputs = model.generate(**input_ids)16print(tokenizer.decode(outputs[0]))
Running the model on a GPU using different precisions
The native weights of this model were exported in bfloat16 precision. You can use float16, which may be faster on certain hardware, indicating the torch_dtype when loading the model. For convenience, the float16 revision of the repo contains a copy of the weights already converted to that precision.
You can also use float32 if you skip the dtype, but no precision increase will occur (model weights will just be upcasted to float32). See examples below.
Using torch.float16
python
1# pip install accelerate2from transformers import AutoTokenizer, AutoModelForCausalLM
3import torch
45tokenizer = AutoTokenizer.from_pretrained("google/gemma-1.1-7b-it")6model = AutoModelForCausalLM.from_pretrained(7"google/gemma-1.1-7b-it",8 device_map="auto",9 torch_dtype=torch.float16,10 revision="float16",11)1213input_text ="Write me a poem about Machine Learning."14input_ids = tokenizer(input_text, return_tensors="pt").to("cuda")1516outputs = model.generate(**input_ids)17print(tokenizer.decode(outputs[0]))
Using torch.bfloat16
python
1# pip install accelerate2from transformers import AutoTokenizer, AutoModelForCausalLM
3import torch
45tokenizer = AutoTokenizer.from_pretrained("google/gemma-2b-it")6model = AutoModelForCausalLM.from_pretrained(7"google/gemma-1.1-7b-it",8 device_map="auto",9 torch_dtype=torch.bfloat16
10)1112input_text ="Write me a poem about Machine Learning."13input_ids = tokenizer(input_text, return_tensors="pt").to("cuda")1415outputs = model.generate(**input_ids)16print(tokenizer.decode(outputs[0]))
Upcasting to torch.float32
python
1# pip install accelerate2from transformers import AutoTokenizer, AutoModelForCausalLM
34tokenizer = AutoTokenizer.from_pretrained("google/gemma-1.1-7b-it")5model = AutoModelForCausalLM.from_pretrained(6"google/gemma-1.1-7b-it",7 device_map="auto"8)910input_text ="Write me a poem about Machine Learning."11input_ids = tokenizer(input_text, return_tensors="pt").to("cuda")1213outputs = model.generate(**input_ids)14print(tokenizer.decode(outputs[0]))
Check this notebook for a comprehensive walkthrough on how to parallelize JAX inference.
Chat Template
The instruction-tuned models use a chat template that must be adhered to for conversational use.
The easiest way to apply it is using the tokenizer's built-in chat template, as shown in the following snippet.
Let's load the model and apply the chat template to a conversation. In this example, we'll start with a single user interaction:
At this point, the prompt contains the following text:
<bos><start_of_turn>user
Write a hello world program<end_of_turn>
<start_of_turn>model
As you can see, each turn is preceded by a <start_of_turn> delimiter and then the role of the entity
(either user, for content supplied by the user, or model for LLM responses). Turns finish with
the <end_of_turn> token.
You can follow this format to build the prompt manually, if you need to do it without the tokenizer's
chat template.
After the prompt is ready, generation can be performed like this:
You can find some fine-tuning scripts under the examples/ directory of google/gemma-7b repository. To adapt them to this model, simply change the model-id to google/gemma-1.1-7b-it.
We provide:
A script to perform Supervised Fine-Tuning (SFT) on UltraChat dataset using QLoRA
A script to perform SFT using FSDP on TPU devices
A notebook that you can run on a free-tier Google Colab instance to perform SFT on the English quotes dataset
Inputs and outputs
Input: Text string, such as a question, a prompt, or a document to be
summarized.
Output: Generated English-language text in response to the input, such
as an answer to a question, or a summary of a document.
Model Data
Data used for model training and how the data was processed.
Training Dataset
These models were trained on a dataset of text data that includes a wide variety
of sources, totaling 6 trillion tokens. Here are the key components:
Web Documents: A diverse collection of web text ensures the model is exposed
to a broad range of linguistic styles, topics, and vocabulary. Primarily
English-language content.
Code: Exposing the model to code helps it to learn the syntax and patterns of
programming languages, which improves its ability to generate code or
understand code-related questions.
Mathematics: Training on mathematical text helps the model learn logical
reasoning, symbolic representation, and to address mathematical queries.
The combination of these diverse data sources is crucial for training a powerful
language model that can handle a wide variety of different tasks and text
formats.
Data Preprocessing
Here are the key data cleaning and filtering methods applied to the training
data:
CSAM Filtering: Rigorous CSAM (Child Sexual Abuse Material) filtering was
applied at multiple stages in the data preparation process to ensure the
exclusion of harmful and illegal content
Sensitive Data Filtering: As part of making Gemma pre-trained models safe and
reliable, automated techniques were used to filter out certain personal
information and other sensitive data from training sets.
Additional methods: Filtering based on content quality and safely in line with
our policies.
Training large language models requires significant computational power. TPUs,
designed specifically for matrix operations common in machine learning, offer
several advantages in this domain:
Performance: TPUs are specifically designed to handle the massive computations
involved in training LLMs. They can speed up training considerably compared to
CPUs.
Memory: TPUs often come with large amounts of high-bandwidth memory, allowing
for the handling of large models and batch sizes during training. This can
lead to better model quality.
Scalability: TPU Pods (large clusters of TPUs) provide a scalable solution for
handling the growing complexity of large foundation models. You can distribute
training across multiple TPU devices for faster and more efficient processing.
Cost-effectiveness: In many scenarios, TPUs can provide a more cost-effective
solution for training large models compared to CPU-based infrastructure,
especially when considering the time and resources saved due to faster
training.
JAX allows researchers to take advantage of the latest generation of hardware,
including TPUs, for faster and more efficient training of large models.
ML Pathways is Google's latest effort to build artificially intelligent systems
capable of generalizing across multiple tasks. This is specially suitable for
foundation models, including large language models like
these ones.
Together, JAX and ML Pathways are used as described in the
paper about the Gemini family of models; "the 'single
controller' programming model of Jax and Pathways allows a single Python
process to orchestrate the entire training run, dramatically simplifying the
development workflow."
Evaluation
Model evaluation metrics and results.
Benchmark Results
The pre-trained base models were evaluated against a large collection of different datasets and
metrics to cover different aspects of text generation:
Ethics and safety evaluation approach and results.
Evaluation Approach
Our evaluation methods include structured evaluations and internal red-teaming
testing of relevant content policies. Red-teaming was conducted by a number of
different teams, each with different goals and human evaluation metrics. These
models were evaluated against a number of different categories relevant to
ethics and safety, including:
Text-to-Text Content Safety: Human evaluation on prompts covering safety
policies including child sexual abuse and exploitation, harassment, violence
and gore, and hate speech.
Text-to-Text Representational Harms: Benchmark against relevant academic
datasets such as WinoBias and BBQ Dataset.
Memorization: Automated evaluation of memorization of training data, including
the risk of personally identifiable information exposure.
Large-scale harm: Tests for "dangerous capabilities," such as chemical,
biological, radiological, and nuclear (CBRN) risks.
Evaluation Results
The results of ethics and safety evaluations are within acceptable thresholds
for meeting internal policies for categories such as child
safety, content safety, representational harms, memorization, large-scale harms.
On top of robust internal evaluations, the results of well known safety
benchmarks like BBQ, BOLD, Winogender, Winobias, RealToxicity, and TruthfulQA
are shown here.
Gemma 1.0
Benchmark
Metric
Gemma 1.0 IT 2B
Gemma 1.0 IT 7B
[RealToxicity][realtox]
average
6.86
7.90
[BOLD][bold]
45.57
49.08
[CrowS-Pairs][crows]
top-1
45.82
51.33
[BBQ Ambig][bbq]
1-shot, top-1
62.58
92.54
[BBQ Disambig][bbq]
top-1
54.62
71.99
[Winogender][winogender]
top-1
51.25
54.17
[TruthfulQA][truthfulqa]
44.84
31.81
[Winobias 1_2][winobias]
56.12
59.09
[Winobias 2_2][winobias]
91.10
92.23
[Toxigen][toxigen]
29.77
39.59
------------------------
-------------
---------------
---------------
Gemma 1.1
Benchmark
Metric
Gemma 1.1 IT 2B
Gemma 1.1 IT 7B
[RealToxicity][realtox]
average
7.03
8.04
[BOLD][bold]
47.76
[CrowS-Pairs][crows]
top-1
45.89
49.67
[BBQ Ambig][bbq]
1-shot, top-1
58.97
86.06
[BBQ Disambig][bbq]
top-1
53.90
85.08
[Winogender][winogender]
top-1
50.14
57.64
[TruthfulQA][truthfulqa]
44.24
45.34
[Winobias 1_2][winobias]
55.93
59.22
[Winobias 2_2][winobias]
89.46
89.2
[Toxigen][toxigen]
29.64
38.75
------------------------
-------------
---------------
---------------
Usage and Limitations
These models have certain limitations that users should be aware of.
Intended Usage
Open Large Language Models (LLMs) have a wide range of applications across
various industries and domains. The following list of potential uses is not
comprehensive. The purpose of this list is to provide contextual information
about the possible use-cases that the model creators considered as part of model
training and development.
Content Creation and Communication
Text Generation: These models can be used to generate creative text formats
such as poems, scripts, code, marketing copy, and email drafts.
Chatbots and Conversational AI: Power conversational interfaces for customer
service, virtual assistants, or interactive applications.
Text Summarization: Generate concise summaries of a text corpus, research
papers, or reports.
Research and Education
Natural Language Processing (NLP) Research: These models can serve as a
foundation for researchers to experiment with NLP techniques, develop
algorithms, and contribute to the advancement of the field.
Language Learning Tools: Support interactive language learning experiences,
aiding in grammar correction or providing writing practice.
Knowledge Exploration: Assist researchers in exploring large bodies of text
by generating summaries or answering questions about specific topics.
Limitations
Training Data
The quality and diversity of the training data significantly influence the
model's capabilities. Biases or gaps in the training data can lead to
limitations in the model's responses.
The scope of the training dataset determines the subject areas the model can
handle effectively.
Context and Task Complexity
LLMs are better at tasks that can be framed with clear prompts and
instructions. Open-ended or highly complex tasks might be challenging.
A model's performance can be influenced by the amount of context provided
(longer context generally leads to better outputs, up to a certain point).
Language Ambiguity and Nuance
Natural language is inherently complex. LLMs might struggle to grasp subtle
nuances, sarcasm, or figurative language.
Factual Accuracy
LLMs generate responses based on information they learned from their
training datasets, but they are not knowledge bases. They may generate
incorrect or outdated factual statements.
Common Sense
LLMs rely on statistical patterns in language. They might lack the ability
to apply common sense reasoning in certain situations.
Ethical Considerations and Risks
The development of large language models (LLMs) raises several ethical concerns.
In creating an open model, we have carefully considered the following:
Bias and Fairness
LLMs trained on large-scale, real-world text data can reflect socio-cultural
biases embedded in the training material. These models underwent careful
scrutiny, input data pre-processing described and posterior evaluations
reported in this card.
Misinformation and Misuse
LLMs can be misused to generate text that is false, misleading, or harmful.
This model card summarizes details on the models' architecture,
capabilities, limitations, and evaluation processes.
A responsibly developed open model offers the opportunity to share
innovation by making LLM technology accessible to developers and researchers
across the AI ecosystem.
Risks identified and mitigations:
Perpetuation of biases: It's encouraged to perform continuous monitoring
(using evaluation metrics, human review) and the exploration of de-biasing
techniques during model training, fine-tuning, and other use cases.
Generation of harmful content: Mechanisms and guidelines for content safety
are essential. Developers are encouraged to exercise caution and implement
appropriate content safety safeguards based on their specific product policies
and application use cases.
Misuse for malicious purposes: Technical limitations and developer and
end-user education can help mitigate against malicious applications of LLMs.
Educational resources and reporting mechanisms for users to flag misuse are
provided. Prohibited uses of Gemma models are outlined in the
Gemma Prohibited Use Policy.
Privacy violations: Models were trained on data filtered for removal of PII
(Personally Identifiable Information). Developers are encouraged to adhere to
privacy regulations with privacy-preserving techniques.
Benefits
At the time of release, this family of models provides high-performance open
large language model implementations designed from the ground up for Responsible
AI development compared to similarly sized models.
Using the benchmark evaluation metrics described in this document, these models
have shown to provide superior performance to other, comparably-sized open model
alternatives.
