Turning Code Manager on also activates "Static Catalogs". These contain pre-computed metadata for

file

resources that use content deployed through Code Manager. This provides two benefits: • An entire source of JRuby contention is eliminated as agents no longer have to make

file_metadata

requests to determine expected checksums, it's all just there in the catalog.

file_content

requests are also cheaper as they stay in the Java layer and hit the JGit service instead of going down to JRuby. • The agent gets file content from the same deployment that its catalog was compiled from. Not a different version that may have come down in a subsequent deployment. IIRC, the above combined into something like a 20% cut to the JRuby load in Puppet Lab's internal infrastructure when it was benchmarked years ago. Milage will vary, custom file mounts serving large blobs are still something to shift over to a dedicated file or artifact server.