A scalability test of the fields_for_wildcard and new fields REST api calls has shown that the processing of larger field_caps responses can be somewhat slow and introduce a fair amount of server load.

Attempts to make the code more efficient have either failed or are too small to make a meaningful difference. Instead, we could move the field_caps response processing to the client. This has the advantage of allowing the browser to skip the processing of the response if its a 304.

We haven't specifically seen any complaints regarding this but I still thought it was worth documenting.