---
schema_version: "1"
id: 226a35786f7cfaf2dc0dad94be7a1759f19f93e0e39688328fff9a122c3ac27b
title: Tableau Server Cache Server
collection: tableau
version: next
locale: en-us
portal_url: https://docs.salesforce.com/tableau/next/en-us/server-linux/server_process_cache-server.md
canonical_url: https://help.tableau.com/v0.0/server-linux/en-us/server_process_cache-server.htm
source_site: help.tableau.com
content_type: documentation
content_hash: e45dcaa6e317e0f42a709f6491100f85de0d4c6d71a62737fc6ab6265bf92643
description: Understand the Tableau Server Cache Server process for query caching.
---
[Skip to main content](#main-content)

# Tableau Server Cache Server

The Cache Server provides a shared external query cache. It’s a cache of key/value pairs which hold information from previous queries to speed up future requests. To make Cache Server highly available, configure one or more Cache Server processes on multiple nodes of the cluster.

<table style="width: 100%;mc-table-style: url('Resources/TableStyles/Basic-Border.css');" class="TableStyle-Basic-Border" cellspacing="0">
                    <colgroup><col class="TableStyle-Basic-Border-Column-Column1">
                    
                    <col class="TableStyle-Basic-Border-Column-Column1">
                    
                    </colgroup><tbody>
                        <tr class="TableStyle-Basic-Border-Body-Body1">
                            <td class="TableStyle-Basic-Border-BodyE-Column1-Body1"><strong>Process</strong>
                            </td>
                            <td class="TableStyle-Basic-Border-BodyD-Column1-Body1">
                                <p>
                                    Cache Server
                                </p>
                            </td>
                        </tr>
                        <tr class="TableStyle-Basic-Border-Body-Body1">
                            <td class="TableStyle-Basic-Border-BodyE-Column1-Body1"><strong>Status</strong>
                            </td>
                            <td class="TableStyle-Basic-Border-BodyD-Column1-Body1">Status of the  Cache Server  process is visible on the Status Page. For more information, see <a href="https://help.tableau.com/v0.0/server-linux/en-us/service_viewstatus.htm" class="xref">View Server Process Status</a></td>
                        </tr>
                        <tr class="TableStyle-Basic-Border-Body-Body1">
                            <td class="TableStyle-Basic-Border-BodyB-Column1-Body1"><strong>Logging</strong>
                            </td>
                            <td class="TableStyle-Basic-Border-BodyA-Column1-Body1">Logs generated by the  Cache Server  process are located in <code><code>/var/opt/tableau/tableau_server/data/tabsvc/logs/</code>cacheserver</code>. For more information, see <a href="https://help.tableau.com/v0.0/server-linux/en-us/logs_loc.htm" class="xref">Tableau Server Logs and Log File Locations</a></td>
                        </tr>
                    </tbody>
                </table>

What happens when Cache Server process goes down? The consequences are relatively mild. Tableau Server will still work but actions may take longer as they do not have cached results available. As the queries rerun, the restarted Cache Server gets repopulated, eventually speeding things up for end users. In effect, Cache Server does not have an availability impact; however, it does have an impact on various end user performance scenarios.

To reduce impact on user performance, run multiple processes of this type across the cluster. We recommend you install no more than a maximum of six cache server instances, limiting each node to no more than two. Our testing indicates that installing more than a total of six cache server instances in a Tableau Server installation provides no improvement, and could have a negative impact on performance.

A failed Cache Server process is automatically restarted; as long as the computer itself is otherwise healthy, the Cache Server process will relaunch.