# Array views becoming dominant source of memory allocation

**URL:** https://discourse.julialang.org/t/array-views-becoming-dominant-source-of-memory-allocation/6465
**Category:** Performance
**Created:** [October 16, 2017, 11:31am UTC](https://discourse.julialang.org/t/array-views-becoming-dominant-source-of-memory-allocation/6465 "2017-10-16T11:31:24Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![rdeits](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/rdeits/32/286_2.png) [@rdeits](https://discourse.julialang.org/u/rdeits)
#### Post date: [October 16, 2017, 4:24pm UTC](https://discourse.julialang.org/t/array-views-becoming-dominant-source-of-memory-allocation/6465/7 "2017-10-16T16:24:08Z")

</div>

I ran into a similar issue when writing [https://github.com/rdeits/NNLS.jl](https://github.com/rdeits/NNLS.jl) and ended up adapting some code by `@tkoolen` so that I could create unsafe but allocation-free views for use inside inner loops like this. I posted about it over ate [Marching cubes without extra allocations - #2 by rdeits](https://discourse.julialang.org/t/marching-cubes-without-extra-allocations/6222/2)

---

_[View the full topic](https://discourse.julialang.org/t/array-views-becoming-dominant-source-of-memory-allocation/6465)._