Impact on performance when custom field context is global?

[DI2E Licensing]

We are reading http://blogs.atlassian.com/2015/05/webinar-recap-five-secrets-jira-performance-scale/ with interest.

Here's my question. We have many custom fields where the available context is not as tight as it should be.  The custom field is available to all issue types in all projects yet is really only used by a single project.  We have a lot of these.  If we go through the exercise of tightening up these contexts will that improve the performance of our JIRA instance?

We do realize there is value in doing this outside of simply performance, but I'm specifically interested in the performance impact at this time.

Thanks!

[MarkW]

Atlassian at one time offered testing results and that can be seen on a historical version of their "Scaling JIRA" page: https://confluence.atlassian.com/pages/viewpage.action?pageId=723519294#ScalingJIRA-Howcustomfieldsaffectperformance

Please note, that those results are from a 5.x version of JIRA and is NOT the current version of the page. Otherwise, I have not seen any other test results of the two.

Current page version is here with results of global only custom fields in JIRA 6.4. 

[Peter Bengov]

Very interesting question. Would also like to know the answer to this