Answers.Body: <p>It all depends on what your template is doing with the global.</p>
  
  <p>If it's doing something to cause multiple database calls, then yes, you'll probably see some improvement (maybe minuscule, maybe more significant).</p>
  
  <p>Anywhere you use a cache tags brings an overhead of one additional database call, so you just need to make sure it's worth it. </p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-09-02T00:04:49.513Z
Answers.LastActivityDate: 2014-09-02T00:04:49.513Z
Answers.UserDisplayName: Brad Bell
Body: <p>I have a global that consists of 1 rich text field and the content is displayed on every page. Does it make sense to cache that? If so, I am assuming it should be cached globally?</p>
  
Tags: <cache><globals>
Title: Does it make sense to cache a Global?
ThreadText: # Does it make sense to cache a Global?
  
  (Asked by: username_0 on 2014-09-01)
  
  I have a global that consists of 1 rich text field and the content is displayed on every page. Does it make sense to cache that? If so, I am assuming it should be cached globally?
  
  **Tags:** cache, globals
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2014-09-02. Score: 2 | Accepted answer
  
  It all depends on what your template is doing with the global.
  
  If it's doing something to cause multiple database calls, then yes, you'll probably see some improvement (maybe minuscule, maybe more significant).
  
  Anywhere you use a cache tags brings an overhead of one additional database call, so you just need to make sure it's worth it.
  
  
  ---
  
  