Real-time collaboration for Jupyter Notebooks, Linux Terminals, LaTeX, VS Code, R IDE, and more,

all in one place.

Real-time collaboration for Jupyter Notebooks, Linux Terminals, LaTeX, VS Code, R IDE, and more,

all in one place.

Python Data Science Handbook

**Views:**

^{92280}

**Kernel:**Python 3

*The text is released under the **CC-BY-NC-ND license**, and code is released under the **MIT license**. If you find this content useful, please consider supporting the work by **buying the book**!*

# High-Performance Pandas: eval() and query()

As we've already seen in previous sections, the power of the PyData stack is built upon the ability of NumPy and Pandas to push basic operations into C via an intuitive syntax: examples are vectorized/broadcasted operations in NumPy, and grouping-type operations in Pandas. While these abstractions are efficient and effective for many common use cases, they often rely on the creation of temporary intermediate objects, which can cause undue overhead in computational time and memory use.

As of version 0.13 (released January 2014), Pandas includes some experimental tools that allow you to directly access C-speed operations without costly allocation of intermediate arrays. These are the `eval()`

and `query()`

functions, which rely on the Numexpr package. In this notebook we will walk through their use and give some rules-of-thumb about when you might think about using them.

## Motivating `query()`

and `eval()`

: Compound Expressions

We've seen previously that NumPy and Pandas support fast vectorized operations; for example, when adding the elements of two arrays:

As discussed in Computation on NumPy Arrays: Universal Functions, this is much faster than doing the addition via a Python loop or comprehension:

But this abstraction can become less efficient when computing compound expressions. For example, consider the following expression:

Because NumPy evaluates each subexpression, this is roughly equivalent to the following:

In other words, *every intermediate step is explicitly allocated in memory*. If the `x`

and `y`

arrays are very large, this can lead to significant memory and computational overhead. The Numexpr library gives you the ability to compute this type of compound expression element by element, without the need to allocate full intermediate arrays. The Numexpr documentation has more details, but for the time being it is sufficient to say that the library accepts a *string* giving the NumPy-style expression you'd like to compute:

The benefit here is that Numexpr evaluates the expression in a way that does not use full-sized temporary arrays, and thus can be much more efficient than NumPy, especially for large arrays. The Pandas `eval()`

and `query()`

tools that we will discuss here are conceptually similar, and depend on the Numexpr package.

`pandas.eval()`

for Efficient Operations

The `eval()`

function in Pandas uses string expressions to efficiently compute operations using `DataFrame`

s. For example, consider the following `DataFrame`

s:

To compute the sum of all four `DataFrame`

s using the typical Pandas approach, we can just write the sum:

The same result can be computed via `pd.eval`

by constructing the expression as a string:

The `eval()`

version of this expression is about 50% faster (and uses much less memory), while giving the same result:

### Operations supported by `pd.eval()`

As of Pandas v0.16, `pd.eval()`

supports a wide range of operations. To demonstrate these, we'll use the following integer `DataFrame`

s:

#### Arithmetic operators

`pd.eval()`

supports all arithmetic operators. For example:

#### Comparison operators

`pd.eval()`

supports all comparison operators, including chained expressions:

#### Bitwise operators

`pd.eval()`

supports the `&`

and `|`

bitwise operators:

In addition, it supports the use of the literal `and`

and `or`

in Boolean expressions:

#### Object attributes and indices

`pd.eval()`

supports access to object attributes via the `obj.attr`

syntax, and indexes via the `obj[index]`

syntax:

#### Other operations

Other operations such as function calls, conditional statements, loops, and other more involved constructs are currently *not* implemented in `pd.eval()`

. If you'd like to execute these more complicated types of expressions, you can use the Numexpr library itself.

`DataFrame.eval()`

for Column-Wise Operations

Just as Pandas has a top-level `pd.eval()`

function, `DataFrame`

s have an `eval()`

method that works in similar ways. The benefit of the `eval()`

method is that columns can be referred to *by name*. We'll use this labeled array as an example:

Using `pd.eval()`

as above, we can compute expressions with the three columns like this:

The `DataFrame.eval()`

method allows much more succinct evaluation of expressions with the columns:

Notice here that we treat *column names as variables* within the evaluated expression, and the result is what we would wish.

### Assignment in DataFrame.eval()

In addition to the options just discussed, `DataFrame.eval()`

also allows assignment to any column. Let's use the `DataFrame`

from before, which has columns `'A'`

, `'B'`

, and `'C'`

:

We can use `df.eval()`

to create a new column `'D'`

and assign to it a value computed from the other columns:

In the same way, any existing column can be modified:

### Local variables in DataFrame.eval()

The `DataFrame.eval()`

method supports an additional syntax that lets it work with local Python variables. Consider the following:

The `@`

character here marks a *variable name* rather than a *column name*, and lets you efficiently evaluate expressions involving the two "namespaces": the namespace of columns, and the namespace of Python objects. Notice that this `@`

character is only supported by the `DataFrame.eval()`

*method*, not by the `pandas.eval()`

*function*, because the `pandas.eval()`

function only has access to the one (Python) namespace.

## DataFrame.query() Method

The `DataFrame`

has another method based on evaluated strings, called the `query()`

method. Consider the following:

As with the example used in our discussion of `DataFrame.eval()`

, this is an expression involving columns of the `DataFrame`

. It cannot be expressed using the `DataFrame.eval()`

syntax, however! Instead, for this type of filtering operation, you can use the `query()`

method:

In addition to being a more efficient computation, compared to the masking expression this is much easier to read and understand. Note that the `query()`

method also accepts the `@`

flag to mark local variables:

## Performance: When to Use These Functions

When considering whether to use these functions, there are two considerations: *computation time* and *memory use*. Memory use is the most predictable aspect. As already mentioned, every compound expression involving NumPy arrays or Pandas `DataFrame`

s will result in implicit creation of temporary arrays: For example, this:

Is roughly equivalent to this:

If the size of the temporary `DataFrame`

s is significant compared to your available system memory (typically several gigabytes) then it's a good idea to use an `eval()`

or `query()`

expression. You can check the approximate size of your array in bytes using this:

On the performance side, `eval()`

can be faster even when you are not maxing-out your system memory. The issue is how your temporary `DataFrame`

s compare to the size of the L1 or L2 CPU cache on your system (typically a few megabytes in 2016); if they are much bigger, then `eval()`

can avoid some potentially slow movement of values between the different memory caches. In practice, I find that the difference in computation time between the traditional methods and the `eval`

/`query`

method is usually not significantâ€“if anything, the traditional method is faster for smaller arrays! The benefit of `eval`

/`query`

is mainly in the saved memory, and the sometimes cleaner syntax they offer.

We've covered most of the details of `eval()`

and `query()`

here; for more information on these, you can refer to the Pandas documentation. In particular, different parsers and engines can be specified for running these queries; for details on this, see the discussion within the "Enhancing Performance" section.