by file system cache, you mean to recreate all the files in the pega temp directory? Also, clearing DB cache/delete temp directory should NOT be the common practice in the first place unless there are some rare scenarios (e.g., system cannot startup).
Adding to what Kevin has mentioned here, you need not delete all contents of temp directory except for PegaRULES_Extract_Marker.txt' file and by deleting this file you are enforcing re-extraction and recompilation of all the libraries and functions on one node.
Yes, I mean to recreate all files in pega temp directory. It could partly be recreated by running the "static assembler". Agreed that DB clear should not be common practice, but after installation of some hotfixes; it is recommended by GCS to do so. In those scenarios; i want to make the experience to front end users seamless. My intention is not to let the end users AND the service consumers (pega is exposed as a service) feel the pinch of cache building (or FUA codes) because of the slowness it creates.
Currently I am aware of static assembler to recreate part of the file cache. Similarly; is there a anything i can do to tell the system to rebuild cache - be it DB or File cache ?
In real time environments, when pega is exposed as a service to hundreds of clients; every second matters and static assembler helps a good deal .. !