View on TensorFlow.org | Run in Google Colab | View source on GitHub | Download notebook |

In TensorFlow 2, eager execution is turned on by default. The user interface is intuitive and flexible (running one-off operations is much easier and faster), but this can come at the expense of performance and deployability.

You can use `tf.function`

to make graphs out of your programs. It is a transformation tool that creates Python-independent dataflow graphs out of your Python code. This will help you create performant and portable models, and it is required to use `SavedModel`

.

This guide will help you conceptualize how `tf.function`

works under the hood, so you can use it effectively.

The main takeaways and recommendations are:

- Debug in eager mode, then decorate with
`@tf.function`

. - Don't rely on Python side effects like object mutation or list appends.
`tf.function`

works best with TensorFlow ops; NumPy and Python calls are converted to constants.

## Setup

```
import tensorflow as tf
```

Define a helper function to demonstrate the kinds of errors you might encounter:

```
import traceback
import contextlib
# Some helper code to demonstrate the kinds of errors you might encounter.
@contextlib.contextmanager
def assert_raises(error_class):
try:
yield
except error_class as e:
print('Caught expected exception \n {}:'.format(error_class))
traceback.print_exc(limit=2)
except Exception as e:
raise e
else:
raise Exception('Expected {} to be raised but no error was raised!'.format(
error_class))
```

## Basics

### Usage

A `Function`

you define (for example by applying the `@tf.function`

decorator) is just like a core TensorFlow operation: You can execute it eagerly; you can compute gradients; and so on.

```
@tf.function # The decorator converts `add` into a `Function`.
def add(a, b):
return a + b
add(tf.ones([2, 2]), tf.ones([2, 2])) # [[2., 2.], [2., 2.]]
```

<tf.Tensor: shape=(2, 2), dtype=float32, numpy= array([[2., 2.], [2., 2.]], dtype=float32)>

```
v = tf.Variable(1.0)
with tf.GradientTape() as tape:
result = add(v, 1.0)
tape.gradient(result, v)
```

<tf.Tensor: shape=(), dtype=float32, numpy=1.0>

You can use `Function`

s inside other `Function`

s.

```
@tf.function
def dense_layer(x, w, b):
return add(tf.matmul(x, w), b)
dense_layer(tf.ones([3, 2]), tf.ones([2, 2]), tf.ones([2]))
```

<tf.Tensor: shape=(3, 2), dtype=float32, numpy= array([[3., 3.], [3., 3.], [3., 3.]], dtype=float32)>

`Function`

s can be faster than eager code, especially for graphs with many small ops. But for graphs with a few expensive ops (like convolutions), you may not see much speedup.

```
import timeit
conv_layer = tf.keras.layers.Conv2D(100, 3)
@tf.function
def conv_fn(image):
return conv_layer(image)
image = tf.zeros([1, 200, 200, 100])
# Warm up
conv_layer(image); conv_fn(image)
print("Eager conv:", timeit.timeit(lambda: conv_layer(image), number=10))
print("Function conv:", timeit.timeit(lambda: conv_fn(image), number=10))
print("Note how there's not much difference in performance for convolutions")
```

Eager conv: 0.00443888600000264 Function conv: 0.004833394000002045 Note how there's not much difference in performance for convolutions

### Tracing

This section exposes how `Function`

works under the hood, including implementation details *which may change in the future*. However, once you understand why and when tracing happens, it's much easier to use `tf.function`

effectively!

#### What is "tracing"?

A `Function`

runs your program in a TensorFlow Graph. However, a `tf.Graph`

cannot represent all the things that you'd write in an eager TensorFlow program. For instance, Python supports polymorphism, but `tf.Graph`

requires its inputs to have a specified data type and dimension. Or you may perform side tasks like reading command-line arguments, raising an error, or working with a more complex Python object; none of these things can run in a `tf.Graph`

.

`Function`

bridges this gap by separating your code in two stages:

1) In the first stage, referred to as "**tracing**", `Function`

creates a new `tf.Graph`

. Python code runs normally, but all TensorFlow operations (like adding two Tensors) are *deferred*: they are captured by the `tf.Graph`

and not run.

2) In the second stage, a `tf.Graph`

which contains everything that was deferred in the first stage is run. This stage is much faster than the tracing stage.

Depending on its inputs, `Function`

will not always run the first stage when it is called. See "Rules of tracing" below to get a better sense of how it makes that determination. Skipping the first stage and only executing the second stage is what gives you TensorFlow's high performance.

When `Function`

does decide to trace, the tracing stage is immediately followed by the second stage, so calling the `Function`

both creates and runs the `tf.Graph`

. Later you will see how you can run only the tracing stage with `get_concrete_function`

.

When we pass arguments of different types into a `Function`

, both stages are run:

```
@tf.function
def double(a):
print("Tracing with", a)
return a + a
print(double(tf.constant(1)))
print()
print(double(tf.constant(1.1)))
print()
print(double(tf.constant("a")))
print()
```

Tracing with Tensor("a:0", shape=(), dtype=int32) tf.Tensor(2, shape=(), dtype=int32) Tracing with Tensor("a:0", shape=(), dtype=float32) tf.Tensor(2.2, shape=(), dtype=float32) Tracing with Tensor("a:0", shape=(), dtype=string) tf.Tensor(b'aa', shape=(), dtype=string)

Note that if you repeatedly call a `Function`

with the same argument type, TensorFlow will skip the tracing stage and reuse a previously traced graph, as the generated graph would be identical.

```
# This doesn't print 'Tracing with ...'
print(double(tf.constant("b")))
```

tf.Tensor(b'bb', shape=(), dtype=string)

You can use `pretty_printed_concrete_signatures()`

to see all of the available traces:

```
print(double.pretty_printed_concrete_signatures())
```

double(a) Args: a: int32 Tensor, shape=() Returns: int32 Tensor, shape=() double(a) Args: a: float32 Tensor, shape=() Returns: float32 Tensor, shape=() double(a) Args: a: string Tensor, shape=() Returns: string Tensor, shape=()

So far, you've seen that `tf.function`

creates a cached, dynamic dispatch layer over TensorFlow's graph tracing logic. To be more specific about the terminology:

- A
`tf.Graph`

is the raw, language-agnostic, portable representation of a TensorFlow computation. - A
`ConcreteFunction`

wraps a`tf.Graph`

. - A
`Function`

manages a cache of`ConcreteFunction`

s and picks the right one for your inputs. `tf.function`

wraps a Python function, returning a`Function`

object.**Tracing**creates a`tf.Graph`

and wraps it in a`ConcreteFunction`

, also known as a**trace.**

#### Rules of tracing

A `Function`

determines whether to reuse a traced `ConcreteFunction`

by computing a **cache key** from an input's args and kwargs. A **cache key** is a key that identifies a `ConcreteFunction`

based on the input args and kwargs of the `Function`

call, according to the following rules (which may change):

- The key generated for a
`tf.Tensor`

is its shape and dtype. - The key generated for a
`tf.Variable`

is a unique variable id. - The key generated for a Python primitive (like
`int`

,`float`

,`str`

) is its value. - The key generated for nested
`dict`

s,`list`

s,`tuple`

s,`namedtuple`

s, and`attr`

s is the flattened tuple of leaf-keys (see`nest.flatten`

). (As a result of this flattening, calling a concrete function with a different nesting structure than the one used during tracing will result in a TypeError). - For all other Python types the key is unique to the object. This way a function or method is traced independently for each instance it is called with.

#### Controlling retracing

Retracing, which is when your `Function`

creates more than one trace, helps ensures that TensorFlow generates correct graphs for each set of inputs. However, tracing is an expensive operation! If your `Function`

retraces a new graph for every call, you'll find that your code executes more slowly than if you didn't use `tf.function`

.

To control the tracing behavior, you can use the following techniques:

- Specify
`input_signature`

in`tf.function`

to limit tracing.

```
@tf.function(input_signature=(tf.TensorSpec(shape=[None], dtype=tf.int32),))
def next_collatz(x):
print("Tracing with", x)
return tf.where(x % 2 == 0, x // 2, 3 * x + 1)
print(next_collatz(tf.constant([1, 2])))
# You specified a 1-D tensor in the input signature, so this should fail.
with assert_raises(ValueError):
next_collatz(tf.constant([[1, 2], [3, 4]]))
# You specified an int32 dtype in the input signature, so this should fail.
with assert_raises(ValueError):
next_collatz(tf.constant([1.0, 2.0]))
```

Tracing with Tensor("x:0", shape=(None,), dtype=int32) tf.Tensor([4 1], shape=(2,), dtype=int32) Caught expected exception <class 'ValueError'>: Caught expected exception <class 'ValueError'>: Traceback (most recent call last): File "/tmp/ipykernel_8296/3551158538.py", line 8, in assert_raises yield File "/tmp/ipykernel_8296/1851403433.py", line 9, in <module> next_collatz(tf.constant([[1, 2], [3, 4]])) ValueError: Python inputs incompatible with input_signature: inputs: ( tf.Tensor( [[1 2] [3 4]], shape=(2, 2), dtype=int32)) input_signature: ( TensorSpec(shape=(None,), dtype=tf.int32, name=None)) Traceback (most recent call last): File "/tmp/ipykernel_8296/3551158538.py", line 8, in assert_raises yield File "/tmp/ipykernel_8296/1851403433.py", line 13, in <module> next_collatz(tf.constant([1.0, 2.0])) ValueError: Python inputs incompatible with input_signature: inputs: ( tf.Tensor([1. 2.], shape=(2,), dtype=float32)) input_signature: ( TensorSpec(shape=(None,), dtype=tf.int32, name=None))

Specify a [None] dimension in

`tf.TensorSpec`

to allow for flexibility in trace reuse.Since TensorFlow matches tensors based on their shape, using a

`None`

dimension as a wildcard will allow`Function`

s to reuse traces for variably-sized input. Variably-sized input can occur if you have sequences of different length, or images of different sizes for each batch (See the Transformer and Deep Dream tutorials for example).

```
@tf.function(input_signature=(tf.TensorSpec(shape=[None], dtype=tf.int32),))
def g(x):
print('Tracing with', x)
return x
# No retrace!
print(g(tf.constant([1, 2, 3])))
print(g(tf.constant([1, 2, 3, 4, 5])))
```

Tracing with Tensor("x:0", shape=(None,), dtype=int32) tf.Tensor([1 2 3], shape=(3,), dtype=int32) tf.Tensor([1 2 3 4 5], shape=(5,), dtype=int32)

Cast Python arguments to Tensors to reduce retracing.

Often, Python arguments are used to control hyperparameters and graph constructions - for example,

`num_layers=10`

or`training=True`

or`nonlinearity='relu'`

. So, if the Python argument changes, it makes sense that you'd have to retrace the graph.However, it's possible that a Python argument is not being used to control graph construction. In these cases, a change in the Python value can trigger needless retracing. Take, for example, this training loop, which AutoGraph will dynamically unroll. Despite the multiple traces, the generated graph is actually identical, so retracing is unnecessary.

```
def train_one_step():
pass
@tf.function
def train(num_steps):
print("Tracing with num_steps = ", num_steps)
tf.print("Executing with num_steps = ", num_steps)
for _ in tf.range(num_steps):
train_one_step()
print("Retracing occurs for different Python arguments.")
train(num_steps=10)
train(num_steps=20)
print()
print("Traces are reused for Tensor arguments.")
train(num_steps=tf.constant(10))
train(num_steps=tf.constant(20))
```

Retracing occurs for different Python arguments. Tracing with num_steps = 10 Executing with num_steps = 10 Tracing with num_steps = 20 Executing with num_steps = 20 Traces are reused for Tensor arguments. Tracing with num_steps = Tensor("num_steps:0", shape=(), dtype=int32) Executing with num_steps = 10 Executing with num_steps = 20

If you need to force retracing, create a new `Function`

. Separate `Function`

objects are guaranteed not to share traces.

```
def f():
print('Tracing!')
tf.print('Executing')
tf.function(f)()
tf.function(f)()
```

Tracing! Executing Tracing! Executing

### Obtaining concrete functions

Every time a function is traced, a new concrete function is created. You can directly obtain a concrete function, by using `get_concrete_function`

.

```
print("Obtaining concrete trace")
double_strings = double.get_concrete_function(tf.constant("a"))
print("Executing traced function")
print(double_strings(tf.constant("a")))
print(double_strings(a=tf.constant("b")))
```

Obtaining concrete trace Executing traced function tf.Tensor(b'aa', shape=(), dtype=string) tf.Tensor(b'bb', shape=(), dtype=string)

```
# You can also call get_concrete_function on an InputSpec
double_strings_from_inputspec = double.get_concrete_function(tf.TensorSpec(shape=[], dtype=tf.string))
print(double_strings_from_inputspec(tf.constant("c")))
```

Tracing with Tensor("a:0", shape=(), dtype=string) tf.Tensor(b'cc', shape=(), dtype=string)

Printing a `ConcreteFunction`

displays a summary of its input arguments (with types) and its output type.

```
print(double_strings)
```

ConcreteFunction double(a) Args: a: string Tensor, shape=() Returns: string Tensor, shape=()

You can also directly retrieve a concrete function's signature.

```
print(double_strings.structured_input_signature)
print(double_strings.structured_outputs)
```

((TensorSpec(shape=(), dtype=tf.string, name='a'),), {}) Tensor("Identity:0", shape=(), dtype=string)

Using a concrete trace with incompatible types will throw an error

```
with assert_raises(tf.errors.InvalidArgumentError):
double_strings(tf.constant(1))
```

Caught expected exception <class 'tensorflow.python.framework.errors_impl.InvalidArgumentError'>: Traceback (most recent call last): File "/tmp/ipykernel_8296/3551158538.py", line 8, in assert_raises yield File "/tmp/ipykernel_8296/3196284684.py", line 2, in <module> double_strings(tf.constant(1)) tensorflow.python.framework.errors_impl.InvalidArgumentError: cannot compute __inference_double_162 as input #0(zero-based) was expected to be a string tensor but is a int32 tensor [Op:__inference_double_162]

You may notice that Python arguments are given special treatment in a concrete function's input signature. Prior to TensorFlow 2.3, Python arguments were simply removed from the concrete function's signature. Starting with TensorFlow 2.3, Python arguments remain in the signature, but are constrained to take the value set during tracing.

```
@tf.function
def pow(a, b):
return a ** b
square = pow.get_concrete_function(a=tf.TensorSpec(None, tf.float32), b=2)
print(square)
```

ConcreteFunction pow(a, b=2) Args: a: float32 Tensor, shape=<unknown> Returns: float32 Tensor, shape=<unknown>

```
assert square(tf.constant(10.0)) == 100
with assert_raises(TypeError):
square(tf.constant(10.0), b=3)
```

Caught expected exception <class 'TypeError'>: Traceback (most recent call last): File "/tmpfs/src/tf_docs_env/lib/python3.7/site-packages/tensorflow/python/eager/function.py", line 1721, in _call_impl cancellation_manager) File "/tmpfs/src/tf_docs_env/lib/python3.7/site-packages/tensorflow/python/eager/function.py", line 1766, in _call_with_flat_signature self._flat_signature_summary(), ", ".join(sorted(kwargs)))) TypeError: pow(a) got unexpected keyword arguments: b. During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/tmp/ipykernel_8296/3551158538.py", line 8, in assert_raises yield File "/tmp/ipykernel_8296/2310937119.py", line 4, in <module> square(tf.constant(10.0), b=3) TypeError: ConcreteFunction pow(a, b) was constructed with int value 2 in b, but was called with int value 3

### Obtaining graphs

Each concrete function is a callable wrapper around a `tf.Graph`

. Although retrieving the actual `tf.Graph`

object is not something you'll normally need to do, you can obtain it easily from any concrete function.

```
graph = double_strings.graph
for node in graph.as_graph_def().node:
print(f'{node.input} -> {node.name}')
```

[] -> a ['a', 'a'] -> add ['add'] -> Identity

### Debugging

In general, debugging code is easier in eager mode than inside `tf.function`

. You should ensure that your code executes error-free in eager mode before decorating with `tf.function`

. To assist in the debugging process, you can call `tf.config.run_functions_eagerly(True)`

to globally disable and reenable `tf.function`

.

When tracking down issues that only appear within `tf.function`

, here are some tips:

- Plain old Python
`print`

calls only execute during tracing, helping you track down when your function gets (re)traced. `tf.print`

calls will execute every time, and can help you track down intermediate values during execution.`tf.debugging.enable_check_numerics`

is an easy way to track down where NaNs and Inf are created.`pdb`

(the Python debugger) can help you understand what's going on during tracing. (Caveat:`pdb`

will drop you into AutoGraph-transformed source code.)

## AutoGraph transformations

AutoGraph is a library that is on by default in `tf.function`

, and transforms a subset of Python eager code into graph-compatible TensorFlow ops. This includes control flow like `if`

, `for`

, `while`

.

TensorFlow ops like `tf.cond`

and `tf.while_loop`

continue to work, but control flow is often easier to write and understand when written in Python.

```
# A simple loop
@tf.function
def f(x):
while tf.reduce_sum(x) > 1:
tf.print(x)
x = tf.tanh(x)
return x
f(tf.random.uniform([5]))
```

[0.134340048 0.12084043 0.899008512 0.317973018 0.984562874] [0.133537665 0.120255642 0.715814829 0.307672977 0.755034447] [0.132749513 0.119679272 0.614310205 0.298318624 0.638142884] [0.131975174 0.119111128 0.547154069 0.289773166 0.56363374] [0.131214246 0.118551008 0.498384237 0.281926 0.510668516] [0.130466327 0.117998719 0.46084547 0.274686694 0.470465899] [0.129731074 0.117454082 0.43077302 0.267980397 0.438575685] [0.129008129 0.116916925 0.405967116 0.261744559 0.412463129] [0.12829715 0.116387077 0.385043025 0.255926549 0.390562057] [0.127597824 0.115864381 0.367079 0.250481546 0.371844649] [0.126909807 0.115348652 0.351434082 0.245371237 0.355604142] [0.126232818 0.11483977 0.337646723 0.240562648 0.341336131] [0.125566557 0.114337578 0.325374842 0.236027122 0.328669697] [0.124910742 0.113841921 0.314358741 0.231739685 0.317324936] [0.124265119 0.113352649 0.304397196 0.227678493 0.30708608] [0.123629414 0.112869643 0.295331478 0.223824292 0.297783881] [0.123003371 0.112392753 0.287034482 0.220160022 0.289283246] [0.122386754 0.111921862 0.279403061 0.216670573 0.281474978] <tf.Tensor: shape=(5,), dtype=float32, numpy= array([0.12177932, 0.11145685, 0.2723525 , 0.21334243, 0.27426964], dtype=float32)>

If you're curious you can inspect the code autograph generates.

```
print(tf.autograph.to_code(f.python_function))
```

def tf__f(x): with ag__.FunctionScope('f', 'fscope', ag__.ConversionOptions(recursive=True, user_requested=True, optional_features=(), internal_convert_user_code=True)) as fscope: do_return = False retval_ = ag__.UndefinedReturnValue() def get_state(): return (x,) def set_state(vars_): nonlocal x (x,) = vars_ def loop_body(): nonlocal x ag__.converted_call(ag__.ld(tf).print, (ag__.ld(x),), None, fscope) x = ag__.converted_call(ag__.ld(tf).tanh, (ag__.ld(x),), None, fscope) def loop_test(): return (ag__.converted_call(ag__.ld(tf).reduce_sum, (ag__.ld(x),), None, fscope) > 1) ag__.while_stmt(loop_test, loop_body, get_state, set_state, ('x',), {}) try: do_return = True retval_ = ag__.ld(x) except: do_return = False raise return fscope.ret(retval_, do_return)

### Conditionals

AutoGraph will convert some `if <condition>`

statements into the equivalent `tf.cond`

calls. This substitution is made if `<condition>`

is a Tensor. Otherwise, the `if`

statement is executed as a Python conditional.

A Python conditional executes during tracing, so exactly one branch of the conditional will be added to the graph. Without AutoGraph, this traced graph would be unable to take the alternate branch if there is data-dependent control flow.

`tf.cond`

traces and adds both branches of the conditional to the graph, dynamically selecting a branch at execution time. Tracing can have unintended side effects; check out AutoGraph tracing effects for more information.

```
@tf.function
def fizzbuzz(n):
for i in tf.range(1, n + 1):
print('Tracing for loop')
if i % 15 == 0:
print('Tracing fizzbuzz branch')
tf.print('fizzbuzz')
elif i % 3 == 0:
print('Tracing fizz branch')
tf.print('fizz')
elif i % 5 == 0:
print('Tracing buzz branch')
tf.print('buzz')
else:
print('Tracing default branch')
tf.print(i)
fizzbuzz(tf.constant(5))
fizzbuzz(tf.constant(20))
```

Tracing for loop Tracing fizzbuzz branch Tracing fizz branch Tracing buzz branch Tracing default branch 1 2 fizz 4 buzz 1 2 fizz 4 buzz fizz 7 8 fizz buzz 11 fizz 13 14 fizzbuzz 16 17 fizz 19 buzz

See the reference documentation for additional restrictions on AutoGraph-converted if statements.

### Loops

AutoGraph will convert some `for`

and `while`

statements into the equivalent TensorFlow looping ops, like `tf.while_loop`

. If not converted, the `for`

or `while`

loop is executed as a Python loop.

This substitution is made in the following situations:

`for x in y`

: if`y`

is a Tensor, convert to`tf.while_loop`

. In the special case where`y`

is a`tf.data.Dataset`

, a combination of`tf.data.Dataset`

ops are generated.`while <condition>`

: if`<condition>`

is a Tensor, convert to`tf.while_loop`

.

A Python loop executes during tracing, adding additional ops to the `tf.Graph`

for every iteration of the loop.

A TensorFlow loop traces the body of the loop, and dynamically selects how many iterations to run at execution time. The loop body only appears once in the generated `tf.Graph`

.

See the reference documentation for additional restrictions on AutoGraph-converted `for`

and `while`

statements.

#### Looping over Python data

A common pitfall is to loop over Python/NumPy data within a `tf.function`

. This loop will execute during the tracing process, adding a copy of your model to the `tf.Graph`

for each iteration of the loop.

If you want to wrap the entire training loop in `tf.function`

, the safest way to do this is to wrap your data as a `tf.data.Dataset`

so that AutoGraph will dynamically unroll the training loop.

```
def measure_graph_size(f, *args):
g = f.get_concrete_function(*args).graph
print("{}({}) contains {} nodes in its graph".format(
f.__name__, ', '.join(map(str, args)), len(g.as_graph_def().node)))
@tf.function
def train(dataset):
loss = tf.constant(0)
for x, y in dataset:
loss += tf.abs(y - x) # Some dummy computation.
return loss
small_data = [(1, 1)] * 3
big_data = [(1, 1)] * 10
measure_graph_size(train, small_data)
measure_graph_size(train, big_data)
measure_graph_size(train, tf.data.Dataset.from_generator(
lambda: small_data, (tf.int32, tf.int32)))
measure_graph_size(train, tf.data.Dataset.from_generator(
lambda: big_data, (tf.int32, tf.int32)))
```

train([(1, 1), (1, 1), (1, 1)]) contains 11 nodes in its graph train([(1, 1), (1, 1), (1, 1), (1, 1), (1, 1), (1, 1), (1, 1), (1, 1), (1, 1), (1, 1)]) contains 32 nodes in its graph train(<FlatMapDataset shapes: (<unknown>, <unknown>), types: (tf.int32, tf.int32)>) contains 6 nodes in its graph train(<FlatMapDataset shapes: (<unknown>, <unknown>), types: (tf.int32, tf.int32)>) contains 6 nodes in its graph

When wrapping Python/NumPy data in a Dataset, be mindful of `tf.data.Dataset.from_generator`

versus `tf.data.Dataset.from_tensors`

. The former will keep the data in Python and fetch it via `tf.py_function`

which can have performance implications, whereas the latter will bundle a copy of the data as one large `tf.constant()`

node in the graph, which can have memory implications.

Reading data from files via `TFRecordDataset`

, `CsvDataset`

, etc. is the most effective way to consume data, as then TensorFlow itself can manage the asynchronous loading and prefetching of data, without having to involve Python. To learn more, see the `tf.data`

: Build TensorFlow input pipelines guide.

#### Accumulating values in a loop

A common pattern is to accumulate intermediate values from a loop. Normally, this is accomplished by appending to a Python list or adding entries to a Python dictionary. However, as these are Python side effects, they will not work as expected in a dynamically unrolled loop. Use `tf.TensorArray`

to accumulate results from a dynamically unrolled loop.

```
batch_size = 2
seq_len = 3
feature_size = 4
def rnn_step(inp, state):
return inp + state
@tf.function
def dynamic_rnn(rnn_step, input_data, initial_state):
# [batch, time, features] -> [time, batch, features]
input_data = tf.transpose(input_data, [1, 0, 2])
max_seq_len = input_data.shape[0]
states = tf.TensorArray(tf.float32, size=max_seq_len)
state = initial_state
for i in tf.range(max_seq_len):
state = rnn_step(input_data[i], state)
states = states.write(i, state)
return tf.transpose(states.stack(), [1, 0, 2])
dynamic_rnn(rnn_step,
tf.random.uniform([batch_size, seq_len, feature_size]),
tf.zeros([batch_size, feature_size]))
```

<tf.Tensor: shape=(2, 3, 4), dtype=float32, numpy= array([[[0.50723314, 0.05389965, 0.6574272 , 0.7971941 ], [0.76342154, 0.67873085, 0.6722325 , 0.80833924], [1.4959786 , 0.92963636, 1.181517 , 0.82988703]], [[0.05639362, 0.30149877, 0.5931294 , 0.58158445], [0.7223501 , 0.7357049 , 1.5900992 , 1.5196564 ], [1.2542304 , 1.443726 , 1.6683336 , 2.2088552 ]]], dtype=float32)>

## Limitations

TensorFlow `Function`

has a few limitations by design that you should be aware of when converting a Python function to a `Function`

.

### Executing Python side effects

Side effects, like printing, appending to lists, and mutating globals, can behave unexpectedly inside a `Function`

, sometimes executing twice or not all. They only happen the first time you call a `Function`

with a set of inputs. Afterwards, the traced `tf.Graph`

is reexecuted, without executing the Python code.

The general rule of thumb is to avoid relying on Python side effects in your logic and only use them to debug your traces. Otherwise, TensorFlow APIs like `tf.data`

, `tf.print`

, `tf.summary`

, `tf.Variable.assign`

, and `tf.TensorArray`

are the best way to ensure your code will be executed by the TensorFlow runtime with each call.

```
@tf.function
def f(x):
print("Traced with", x)
tf.print("Executed with", x)
f(1)
f(1)
f(2)
```

Traced with 1 Executed with 1 Executed with 1 Traced with 2 Executed with 2

If you would like to execute Python code during each invocation of a `Function`

, `tf.py_function`

is an exit hatch. The drawback of `tf.py_function`

is that it's not portable or particularly performant, cannot be saved with SavedModel, and does not work well in distributed (multi-GPU, TPU) setups. Also, since `tf.py_function`

has to be wired into the graph, it casts all inputs/outputs to tensors.

#### Changing Python global and free variables

Changing Python global and free variables counts as a Python side effect, so it only happens during tracing.

```
external_list = []
@tf.function
def side_effect(x):
print('Python side effect')
external_list.append(x)
side_effect(1)
side_effect(1)
side_effect(1)
# The list append only happened once!
assert len(external_list) == 1
```

Python side effect

You should avoid mutating containers like lists, dicts, other objects that live outside the `Function`

. Instead, use arguments and TF objects. For example, the section "Accumulating values in a loop" has one example of how list-like operations can be implemented.

You can, in some cases, capture and manipulate state if it is a `tf.Variable`

. This is how the weights of Keras models are updated with repeated calls to the same `ConcreteFunction`

.

#### Using Python iterators and generators

Many Python features, such as generators and iterators, rely on the Python runtime to keep track of state. In general, while these constructs work as expected in eager mode, they are examples of Python side effects and therefore only happen during tracing.

```
@tf.function
def buggy_consume_next(iterator):
tf.print("Value:", next(iterator))
iterator = iter([1, 2, 3])
buggy_consume_next(iterator)
# This reuses the first value from the iterator, rather than consuming the next value.
buggy_consume_next(iterator)
buggy_consume_next(iterator)
```

Value: 1 Value: 1 Value: 1

Just like how TensorFlow has a specialized `tf.TensorArray`

for list constructs, it has a specialized `tf.data.Iterator`

for iteration constructs. See the section on AutoGraph transformations for an overview. Also, the `tf.data`

API can help implement generator patterns:

```
@tf.function
def good_consume_next(iterator):
# This is ok, iterator is a tf.data.Iterator
tf.print("Value:", next(iterator))
ds = tf.data.Dataset.from_tensor_slices([1, 2, 3])
iterator = iter(ds)
good_consume_next(iterator)
good_consume_next(iterator)
good_consume_next(iterator)
```

Value: 1 Value: 2 Value: 3

### Deleting tf.Variables between `Function`

calls

Another error you may encounter is a garbage-collected variable. `ConcreteFunction`

s only retain WeakRefs to the variables they close over, so you must retain a reference to any variables.

```
external_var = tf.Variable(3)
@tf.function
def f(x):
return x * external_var
traced_f = f.get_concrete_function(4)
print("Calling concrete function...")
print(traced_f(4))
# The original variable object gets garbage collected, since there are no more
# references to it.
external_var = tf.Variable(4)
print()
print("Calling concrete function after garbage collecting its closed Variable...")
with assert_raises(tf.errors.FailedPreconditionError):
traced_f(4)
```

Calling concrete function... tf.Tensor(12, shape=(), dtype=int32) Calling concrete function after garbage collecting its closed Variable... Caught expected exception <class 'tensorflow.python.framework.errors_impl.FailedPreconditionError'>: Traceback (most recent call last): File "/tmp/ipykernel_8296/3551158538.py", line 8, in assert_raises yield File "/tmp/ipykernel_8296/3862898592.py", line 16, in <module> traced_f(4) tensorflow.python.framework.errors_impl.FailedPreconditionError: 2 root error(s) found. (0) Failed precondition: Could not find variable _AnonymousVar3. This could mean that the variable has been deleted. In TF1, it can also mean the variable is uninitialized. Debug info: container=localhost, status=Not found: Resource localhost/_AnonymousVar3/N10tensorflow3VarE does not exist. [[node ReadVariableOp (defined at tmp/ipykernel_8296/3862898592.py:4) ]] (1) Failed precondition: Could not find variable _AnonymousVar3. This could mean that the variable has been deleted. In TF1, it can also mean the variable is uninitialized. Debug info: container=localhost, status=Not found: Resource localhost/_AnonymousVar3/N10tensorflow3VarE does not exist. [[node ReadVariableOp (defined at tmp/ipykernel_8296/3862898592.py:4) ]] [[ReadVariableOp/_2]] 0 successful operations. 0 derived errors ignored. [Op:__inference_f_772] Function call stack: f -> f

### All outputs of a tf.function must be return values

With the exception of `tf.Variable`

s, a tf.function must return all its
outputs. Attempting to directly access any tensors from a function without
going through return values causes "leaks".

For example, the function below "leaks" the tensor `a`

through the Python
global `x`

:

```
x = None
@tf.function
def leaky_function(a):
global x
x = a + 1 # Bad - leaks local tensor
return a + 2
correct_a = leaky_function(tf.constant(1))
print(correct_a.numpy()) # Good - value obtained from function's returns
with assert_raises(AttributeError):
x.numpy() # Bad - tensor leaked from inside the function, cannot be used here
print(x)
```

3 Caught expected exception <class 'AttributeError'>: Tensor("add:0", shape=(), dtype=int32) Traceback (most recent call last): File "/tmp/ipykernel_8296/3551158538.py", line 8, in assert_raises yield File "/tmp/ipykernel_8296/1216349822.py", line 13, in <module> x.numpy() # Bad - tensor leaked from inside the function, cannot be used here AttributeError: 'Tensor' object has no attribute 'numpy'

This is true even if the leaked value is also returned:

```
@tf.function
def leaky_function(a):
global x
x = a + 1 # Bad - leaks local tensor
return x # Good - uses local tensor
correct_a = leaky_function(tf.constant(1))
print(correct_a.numpy()) # Good - value obtained from function's returns
with assert_raises(AttributeError):
x.numpy() # Bad - tensor leaked from inside the function, cannot be used here
print(x)
```

2 Caught expected exception <class 'AttributeError'>: Tensor("add:0", shape=(), dtype=int32) Traceback (most recent call last): File "/tmp/ipykernel_8296/3551158538.py", line 8, in assert_raises yield File "/tmp/ipykernel_8296/3201904755.py", line 11, in <module> x.numpy() # Bad - tensor leaked from inside the function, cannot be used here AttributeError: 'Tensor' object has no attribute 'numpy'

You may encounter `TypeError: tf.Graph captured an external symbolic tensor.`

when you use the leaked symbolic tensor in another tf.Graph. For example,

```
@tf.function
def captures_leaked_tensor(b):
b += x # Bad - `x` is leaked from `leaky_function`
return b
# `x` leaked from `leaky_function` is captured by `captures_leaked_tensor`.
with assert_raises(TypeError):
captures_leaked_tensor(tf.constant(2))
concrete_func = captures_leaked_tensor.get_concrete_function(tf.constant(2))
print(concrete_func.captured_inputs)
assert x is concrete_func.captured_inputs[0]
```

Caught expected exception <class 'TypeError'>: [<tf.Tensor 'add:0' shape=() dtype=int32>] Traceback (most recent call last): File "/tmp/ipykernel_8296/3551158538.py", line 8, in assert_raises yield File "/tmp/ipykernel_8296/2761600771.py", line 8, in <module> captures_leaked_tensor(tf.constant(2)) TypeError: An op outside of the function building code is being passed a "Graph" tensor. It is possible to have Graph tensors leak out of the function building context by including a tf.init_scope in your function building code. For example, the following function will fail: @tf.function def has_init_scope(): my_constant = tf.constant(1.) with tf.init_scope(): added = my_constant * 2 The graph tensor has name: add:0

Usually, leaks such as these occur when you use Python statements or data structures. In addition to leaking inaccessible tensors, such statements are also likely wrong because they count as Python side effects, and are not guaranteed to execute at every function call.

Common ways to leak local tensors also include mutating an external Python collection, or an object:

```
class MyClass:
def __init__(self):
self.field = None
external_list = []
external_object = MyClass()
def leaky_function():
a = tf.constant(1)
external_list.append(a) # Bad - leaks tensor
external_object.field = a # Bad - leaks tensor
```

## Known Issues

If your `Function`

is not evaluating correctly, the error may be explained by these known issues which are planned to be fixed in the future.

### Depending on Python global and free variables

`Function`

creates a new `ConcreteFunction`

when called with a new value of a Python argument. However, it does not do that for the Python closure, globals, or nonlocals of that `Function`

. If their value changes in between calls to the `Function`

, the `Function`

will still use the values they had when it was traced. This is different from how regular Python functions work.

For that reason, we recommend a functional programming style that uses arguments instead of closing over outer names.

```
@tf.function
def buggy_add():
return 1 + foo
@tf.function
def recommended_add(foo):
return 1 + foo
foo = 1
print("Buggy:", buggy_add())
print("Correct:", recommended_add(foo))
```

Buggy: tf.Tensor(2, shape=(), dtype=int32) Correct: tf.Tensor(2, shape=(), dtype=int32)

```
print("Updating the value of `foo` to 100!")
foo = 100
print("Buggy:", buggy_add()) # Did not change!
print("Correct:", recommended_add(foo))
```

Updating the value of `foo` to 100! Buggy: tf.Tensor(2, shape=(), dtype=int32) Correct: tf.Tensor(101, shape=(), dtype=int32)

You can close over outer names, as long as you don't update their values.

#### Depending on Python objects

The recommendation to pass Python objects as arguments into `tf.function`

has a number of known issues, that are expected to be fixed in the future. In general, you can rely on consistent tracing if you use a Python primitive or `tf.nest`

-compatible structure as an argument or pass in a *different* instance of an object into a `Function`

. However, `Function`

will *not* create a new trace when you pass **the same object and only change its attributes**.

```
class SimpleModel(tf.Module):
def __init__(self):
# These values are *not* tf.Variables.
self.bias = 0.
self.weight = 2.
@tf.function
def evaluate(model, x):
return model.weight * x + model.bias
simple_model = SimpleModel()
x = tf.constant(10.)
print(evaluate(simple_model, x))
```

tf.Tensor(20.0, shape=(), dtype=float32)

```
print("Adding bias!")
simple_model.bias += 5.0
print(evaluate(simple_model, x)) # Didn't change :(
```

Adding bias! tf.Tensor(20.0, shape=(), dtype=float32)

Using the same `Function`

to evaluate the updated instance of the model will be buggy since the updated model has the same cache key as the original model.

For that reason, we recommend that you write your `Function`

to avoid depending on mutable object attributes or create new objects.

If that is not possible, one workaround is to make new `Function`

s each time you modify your object to force retracing:

```
def evaluate(model, x):
return model.weight * x + model.bias
new_model = SimpleModel()
evaluate_no_bias = tf.function(evaluate).get_concrete_function(new_model, x)
# Don't pass in `new_model`, `Function` already captured its state during tracing.
print(evaluate_no_bias(x))
```

tf.Tensor(20.0, shape=(), dtype=float32)

```
print("Adding bias!")
new_model.bias += 5.0
# Create new Function and ConcreteFunction since you modified new_model.
evaluate_with_bias = tf.function(evaluate).get_concrete_function(new_model, x)
print(evaluate_with_bias(x)) # Don't pass in `new_model`.
```

Adding bias! tf.Tensor(25.0, shape=(), dtype=float32)

As retracing can be expensive, you can use `tf.Variable`

s as object attributes, which can be mutated (but not changed, careful!) for a similar effect without needing a retrace.

```
class BetterModel:
def __init__(self):
self.bias = tf.Variable(0.)
self.weight = tf.Variable(2.)
@tf.function
def evaluate(model, x):
return model.weight * x + model.bias
better_model = BetterModel()
print(evaluate(better_model, x))
```

tf.Tensor(20.0, shape=(), dtype=float32)

```
print("Adding bias!")
better_model.bias.assign_add(5.0) # Note: instead of better_model.bias += 5
print(evaluate(better_model, x)) # This works!
```

Adding bias! tf.Tensor(25.0, shape=(), dtype=float32)

### Creating tf.Variables

`Function`

only supports singleton `tf.Variable`

s created once on the first call, and reused across subsequent function calls. The code snippet below would create a new `tf.Variable`

in every function call, which results in a `ValueError`

exception.

Example:

```
@tf.function
def f(x):
v = tf.Variable(1.0)
return v
with assert_raises(ValueError):
f(1.0)
```

Caught expected exception <class 'ValueError'>: Traceback (most recent call last): File "/tmp/ipykernel_8296/3551158538.py", line 8, in assert_raises yield File "/tmp/ipykernel_8296/3018268426.py", line 7, in <module> f(1.0) ValueError: in user code: /tmp/ipykernel_8296/3018268426.py:3 f * v = tf.Variable(1.0) /tmpfs/src/tf_docs_env/lib/python3.7/site-packages/tensorflow/python/ops/variables.py:268 __call__ ** return cls._variable_v2_call(*args, **kwargs) /tmpfs/src/tf_docs_env/lib/python3.7/site-packages/tensorflow/python/ops/variables.py:262 _variable_v2_call shape=shape) /tmpfs/src/tf_docs_env/lib/python3.7/site-packages/tensorflow/python/ops/variables.py:67 getter return captured_getter(captured_previous, **kwargs) /tmpfs/src/tf_docs_env/lib/python3.7/site-packages/tensorflow/python/eager/def_function.py:765 invalid_creator_scope "tf.function-decorated function tried to create " ValueError: tf.function-decorated function tried to create variables on non-first call.

A common pattern used to work around this limitation is to start with a Python None value, then conditionally create the `tf.Variable`

if the value is None:

```
class Count(tf.Module):
def __init__(self):
self.count = None
@tf.function
def __call__(self):
if self.count is None:
self.count = tf.Variable(0)
return self.count.assign_add(1)
c = Count()
print(c())
print(c())
```

tf.Tensor(1, shape=(), dtype=int32) tf.Tensor(2, shape=(), dtype=int32)

#### Using with multiple Keras optimizers

You may encounter `ValueError: tf.function only supports singleton tf.Variables created on the first call.`

when using more than one Keras optimizer with a `tf.function`

. This error occurs because optimizers internally create `tf.Variables`

when they apply gradients for the first time.

```
opt1 = tf.keras.optimizers.Adam(learning_rate = 1e-2)
opt2 = tf.keras.optimizers.Adam(learning_rate = 1e-3)
@tf.function
def train_step(w, x, y, optimizer):
with tf.GradientTape() as tape:
L = tf.reduce_sum(tf.square(w*x - y))
gradients = tape.gradient(L, [w])
optimizer.apply_gradients(zip(gradients, [w]))
w = tf.Variable(2.)
x = tf.constant([-1.])
y = tf.constant([2.])
train_step(w, x, y, opt1)
print("Calling `train_step` with different optimizer...")
with assert_raises(ValueError):
train_step(w, x, y, opt2)
```

Calling `train_step` with different optimizer... Caught expected exception <class 'ValueError'>: Traceback (most recent call last): File "/tmp/ipykernel_8296/3551158538.py", line 8, in assert_raises yield File "/tmp/ipykernel_8296/3167358578.py", line 18, in <module> train_step(w, x, y, opt2) ValueError: in user code: /tmp/ipykernel_8296/3167358578.py:9 train_step * optimizer.apply_gradients(zip(gradients, [w])) /tmpfs/src/tf_docs_env/lib/python3.7/site-packages/keras/optimizer_v2/optimizer_v2.py:628 apply_gradients ** self._create_all_weights(var_list) /tmpfs/src/tf_docs_env/lib/python3.7/site-packages/keras/optimizer_v2/optimizer_v2.py:813 _create_all_weights _ = self.iterations /tmpfs/src/tf_docs_env/lib/python3.7/site-packages/keras/optimizer_v2/optimizer_v2.py:820 __getattribute__ return super(OptimizerV2, self).__getattribute__(name) /tmpfs/src/tf_docs_env/lib/python3.7/site-packages/keras/optimizer_v2/optimizer_v2.py:980 iterations aggregation=tf.VariableAggregation.ONLY_FIRST_REPLICA) /tmpfs/src/tf_docs_env/lib/python3.7/site-packages/keras/optimizer_v2/optimizer_v2.py:1186 add_weight aggregation=aggregation) /tmpfs/src/tf_docs_env/lib/python3.7/site-packages/tensorflow/python/training/tracking/base.py:818 _add_variable_with_custom_getter **kwargs_for_getter) /tmpfs/src/tf_docs_env/lib/python3.7/site-packages/keras/engine/base_layer_utils.py:129 make_variable shape=variable_shape if variable_shape else None) /tmpfs/src/tf_docs_env/lib/python3.7/site-packages/tensorflow/python/ops/variables.py:266 __call__ return cls._variable_v1_call(*args, **kwargs) /tmpfs/src/tf_docs_env/lib/python3.7/site-packages/tensorflow/python/ops/variables.py:227 _variable_v1_call shape=shape) /tmpfs/src/tf_docs_env/lib/python3.7/site-packages/tensorflow/python/ops/variables.py:67 getter return captured_getter(captured_previous, **kwargs) /tmpfs/src/tf_docs_env/lib/python3.7/site-packages/tensorflow/python/eager/def_function.py:765 invalid_creator_scope "tf.function-decorated function tried to create " ValueError: tf.function-decorated function tried to create variables on non-first call.

If you need to change the optimizer during training, a workaround is to create a new `Function`

for each optimizer, calling the `ConcreteFunction`

directly.

```
opt1 = tf.keras.optimizers.Adam(learning_rate = 1e-2)
opt2 = tf.keras.optimizers.Adam(learning_rate = 1e-3)
# Not a tf.function.
def train_step(w, x, y, optimizer):
with tf.GradientTape() as tape:
L = tf.reduce_sum(tf.square(w*x - y))
gradients = tape.gradient(L, [w])
optimizer.apply_gradients(zip(gradients, [w]))
w = tf.Variable(2.)
x = tf.constant([-1.])
y = tf.constant([2.])
# Make a new Function and ConcreteFunction for each optimizer.
train_step_1 = tf.function(train_step).get_concrete_function(w, x, y, opt1)
train_step_2 = tf.function(train_step).get_concrete_function(w, x, y, opt2)
for i in range(10):
if i % 2 == 0:
train_step_1(w, x, y) # `opt1` is not used as a parameter.
else:
train_step_2(w, x, y) # `opt2` is not used as a parameter.
```

#### Using with multiple Keras models

You may also encounter `ValueError: tf.function only supports singleton tf.Variables created on the first call.`

when passing different model instances to the same `Function`

.

This error occurs because Keras models (which do not have their input shape defined) and Keras layers create `tf.Variables`

s when they are first called. You may be attempting to initialize those variables inside a `Function`

, which has already been called. To avoid this error, try calling `model.build(input_shape)`

to initialize all the weights before training the model.

## Further reading

To learn about how to export and load a `Function`

, see the SavedModel guide. To learn more about graph optimizations that are performed after tracing, see the Grappler guide. To learn how to optimize your data pipeline and profile your model, see the Profiler guide.