# Impact of specifying input types on function performance, when referencing arguments from Vector{Any}

**URL:** <https://discourse.julialang.org/t/impact-of-specifying-input-types-on-function-performance-when-referencing-arguments-from-vector-any/89993>\
**Category:** Performance\
**Created:** [November 9, 2022, 3:39pm UTC](https://discourse.julialang.org/t/impact-of-specifying-input-types-on-function-performance-when-referencing-arguments-from-vector-any/89993 "2022-11-09T15:39:11Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![user664303](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/user664303/32/37843_2.png) [@user664303](https://discourse.julialang.org/u/user664303)\
**Post date:** [November 10, 2022, 11:36am UTC](https://discourse.julialang.org/t/impact-of-specifying-input-types-on-function-performance-when-referencing-arguments-from-vector-any/89993/17 "2022-11-10T11:36:34Z")

</div>

OK, this was a bottom up attempt to fix the performance issues I’m seeing - dive into the code to see where allocations happen, and fix them. I’ve decided to also take a top down approach - describe the type of program I’m trying to write, and see what architectural approaches have already been used in this case. If you’re interested, you can [read about it here](https://discourse.julialang.org/t/how-to-reduce-type-instability-performance-issues-in-general-problem-interfaces/90045).

---

_[View the full topic](https://discourse.julialang.org/t/impact-of-specifying-input-types-on-function-performance-when-referencing-arguments-from-vector-any/89993)._