How to disable cross asset validation in Studio to improve Studio performance and avoid slowness when dealing with large vocabularies?
Deleting vocabulary elements such as attributes or making changes to attributes or the vocabulary in studio takes a long time ( > 5 min ) if the vocabulary is large. Is there a configuration in Studio to avoid this delay ?

There is a known issue with performance with large Vocabularies that has inheritance between many Entities. When inheritance is in play, the Vocabulary Validator has to ensure Attribute uniqueness over its parents and descendants. This can take some time.  

Validation process is itself slow, particularly for large Vocabularies, and to a great degree it comes down to a single method that deals with inheritance. Any time a significant change like the addition or removal of an attribute occurs, or even just a name change, the system has to do a lot to ensure that there are no naming conflicts.We can improve this vastly by defeating the validation for the sake of performance. 

Whenever the Vocabulary is changed, the system will automatically trigger validations in all open assets, that is all Rulesheet, Ruleflow and Ruletest assets that are associated with that Vocabulary. By default we roll out with this dynamic validation enabled. The problem is that when the user has a large number of assets open, it can take a long time. To mitigate this, there are a couple of options: 

a) The user can simply close all assets and work on just the Vocabulary; validation of related assets will be deferred until they are re-opened. This will spread the work out and improve perceived performance. This is the technique that we would use if the user is envisioning a set of substantial changes, and this way the related assets will only trigger revalidation once they are opened. 

b) The user can defeat automatic validation by setting the property com.corticon.resource.validate.on.activation in  brms.properties to true: 
This will cause the system to defer validation of the related assets until their editors are activated (i.e., the user clicks the editor tab). Validate of activation loses the dynamic feedback, but improves performance. 

Property details and descritpion
com.corticon.resource.validate.on.activation controls cross-asset validation behavior. The default setting false causes cross-asset validation to occur immediately whenever any change is made. Consider an example where a Vocabulary Editor and three associated Rulesheet Editors are open simultaneously. Under the default setting of false, a Vocabulary update will cause the Rulesheets to revalidate themselves in real time. This dynamic validation provides instant feedback but carries a performance cost. The alternative setting true causes cross-asset validation to be deferred until the associated editor is activated. In the prior example, a Vocabulary update will trigger only Vocabulary validation rules.Rulesheet Editors will not automatically revalidate themselves until they are activated. This setting can improve performance at the expense of immediate feedback. Default value is false. ( i.e. com.corticon.resource.validate.on.activation=false )