# High usage memory when using and integrating dynamo and pyrevit

**URL:** <https://forum.dynamobim.com/t/high-usage-memory-when-using-and-integrating-dynamo-and-pyrevit/102128>\
**Category:** Revit\
**Tags:** revit, python, dynamo\
**Created:** [June 23, 2024, 10:47am UTC](https://forum.dynamobim.com/t/high-usage-memory-when-using-and-integrating-dynamo-and-pyrevit/102128 "2024-06-23T10:47:31Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![jacob.small](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.dynamobim.com/jacob.small/32/161030_2.png) [@jacob.small](https://forum.dynamobim.com/u/jacob.small)\
**Post date:** [June 23, 2024, 2:20pm UTC](https://forum.dynamobim.com/t/high-usage-memory-when-using-and-integrating-dynamo-and-pyrevit/102128/4 "2024-06-23T14:20:36Z")

</div>

Double check to ensure there are not element bindings, as slow to trigger the UI indicates that is at least part of the issue.

> [@Element Binding in Revit](https://forum.dynamobim.com/t/element-binding-in-revit/31612):
>
> Element binding is the name given to the process which Dynamo manage to ‘track’ the items created in non-Dynamo files. In this case, I’m going to focus entirely on element binding as it refers to Dynamo for Revit, but the mechanism exists to allow for this behavior in other applications (advanced steel, fusion, alias, etc.) as well. In the context of Revit, ‘elements’ refers to anything with an Element ID in the Revit database. When utilized correctly, element binding will expand how you leverag…

---

_[View the full topic](https://forum.dynamobim.com/t/high-usage-memory-when-using-and-integrating-dynamo-and-pyrevit/102128)._