Site Cache enabled with TTL versus disabled for immediate external file visibility on large sites

A design workflow requires the Dreamweaver Files panel to reflect changes made to site files outside of Dreamweaver, such as edits from external editors or version control, while keeping navigation responsive on a large or network-mounted site.

Site Cache enabled stores a local index of file names, timestamps and site-map data. The Files panel and site-wide features populate quickly without scanning the filesystem on each request, but files modified externally are not reflected until the cache is manually refreshed or the configured TTL expires. Site Cache disabled forces Dreamweaver to query the filesystem directly for every operation, which guarantees current state in the panel but can reduce responsiveness on large local sites and network locations.

The decision is between accepting a window of stale listings for performance, or accepting slower panel operations for immediate freshness. What is the appropriate configuration for a team that alternates between active design sessions and external commits? Should Site Cache remain enabled with a shorter TTL, or be disabled during commit windows? How does the Refresh command interact with TTL expiration for external changes?