by Dan Iverson
Bookmark

#160 – Preloading Cache


This week on the podcast, Kyle shares his thoughts on apply CPU vs. PSU java patches and Dan explains the different options for preloading application server cache.

Show Notes

3 thoughts on “#160 – Preloading Cache”

  1. Thank you for going over the different options for preloading application server cache, this was very helpful!

    I am already beginning to test out the shared cache method and I am blown away by the difference in performance. In regards to keeping this cache updated after migrations, did you need to bounce the application server domains so they recognize the new cache files?

    Reply

    1. We haven’t bounce the app servers after building the new shared cache files. Our batch job has a script at the end to copy the new cache files from the STAGE folder to the SHARE folder and we don’t restart the app servers. You’ll want to make sure that’s the case for you. It should be easy to test and verify on your end.

      Reply

  2. Another trick is to do full cache load once, distribute cache files, but then leave the appserver set for doing normal cache activity. This will allow each PSAPPSRV to load new objects as they change, while having the full base set. This might be a strategy for running full load once/wk or once/month and letting the system update by process for any migrations in between.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

To create code blocks or other preformatted text, indent by four spaces:

    This will be displayed in a monospaced font. The first four 
    spaces will be stripped off, but all other whitespace
    will be preserved.
    
    Markdown is turned off in code blocks:
     [This is not a link](http://example.com)

To create not a block, but an inline code span, use backticks: 

Here is some inline `code`.

For more help see http://daringfireball.net/projects/markdown/syntax