# How to investigate output of type instability checks?

**URL:** <https://discourse.julialang.org/t/how-to-investigate-output-of-type-instability-checks/115639>\
**Category:** Performance\
**Tags:** code\_warntype, type-stability\
**Created:** [June 14, 2024, 11:19am UTC](https://discourse.julialang.org/t/how-to-investigate-output-of-type-instability-checks/115639 "2024-06-14T11:19:46Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![Uranium238](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/uranium238/32/209706_2.png) [@Uranium238](https://discourse.julialang.org/u/Uranium238)\
**Post date:** [June 15, 2024, 9:41am UTC](https://discourse.julialang.org/t/how-to-investigate-output-of-type-instability-checks/115639/8 "2024-06-15T09:41:50Z")

</div>

> [@abraemer](#):
>
> Why not keep the values in memory?

That is precisely what I am trying to avoid. These tensors `g_xxxx` will become very large and we want to read these files from the disk only when the part where they would be needed comes up. I know the code attached may not be very clear on this, but [my other post](https://discourse.julialang.org/t/how-to-delete-a-variable-from-memory-in-julia/115649) talks about dealing with this issue.

---

_[View the full topic](https://discourse.julialang.org/t/how-to-investigate-output-of-type-instability-checks/115639)._