# Overhead of UDT Drop Config

**URL:** <https://forum.inductiveautomation.com/t/overhead-of-udt-drop-config/94663>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [August 14, 2024, 5:45pm UTC](https://forum.inductiveautomation.com/t/overhead-of-udt-drop-config/94663 "2024-08-14T17:45:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![brandon1](https://avatars.discourse-cdn.com/v4/letter/b/ea666f/32.png) [@brandon1](https://forum.inductiveautomation.com/u/brandon1)\
**Post date:** [August 14, 2024, 5:45pm UTC](https://forum.inductiveautomation.com/t/overhead-of-udt-drop-config/94663/1 "2024-08-14T17:45:30Z")

</div>

In our project library we have a control button template that has a lot of dropConfig/udts configured:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/5/b5bd1059223f69ec113463c26e13daa549cf72d5.png)

What if any overhead is there for loading this object with all of the dropConfig verses no dropConfig? If I put a disabled binding on it to do a 1 shot configuration of this structure to match our created UDTs will that add a lot of overhead?

Thanks

---

<div class="post-metadata">

**Author:** ![Benjamin\_Furlani](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/benjamin_furlani/32/66084_2.png) [@Benjamin\_Furlani](https://forum.inductiveautomation.com/u/Benjamin_Furlani)\
**Post date:** [August 15, 2024, 7:01pm UTC](https://forum.inductiveautomation.com/t/overhead-of-udt-drop-config/94663/2 "2024-08-15T19:01:39Z")

</div>

Take a look here: [Drop Configuration | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.1/ignition-modules/perspective/working-with-perspective-components/bindings-in-perspective/tag-bindings-in-perspective/drop-configuration)

The dropConfig options are for designer actions when dragging a tag into a view to say what that tag will do in terms of embedded views, bindings, etc.

I wouldn't imagine this has any overhead on the actual view loading into the dom because the screens are already loaded at that point into the browser.