shared_memory takes the listed portions of the database and saves them into files in the shared_memory folder, allowing them to be quickly and easily loaded directly into memory instead of being queried from the database each time they're accessed by each different process.
So, yeah, once it's done its refresh of those files from the database, its work is done until you make a change to the database. It's simplest to have it run each time you start your server, so you don't have to worry about whether or not you've made an applicable change that needs shared_memory to be run again.
|