# Fast tile search

**URL:** https://discourse.julialang.org/t/fast-tile-search/89821
**Category:** GPU
**Created:** [November 5, 2022, 7:19pm UTC](https://discourse.julialang.org/t/fast-tile-search/89821 "2022-11-05T19:19:53Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![00shiv](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/00shiv/32/8903_2.png) [@00shiv](https://discourse.julialang.org/u/00shiv)
#### Post date: [November 11, 2022, 7:23pm UTC](https://discourse.julialang.org/t/fast-tile-search/89821/5 "2022-11-11T19:23:01Z")

</div>

Does anyone know if the techniques on dynamic shared memory from this old thread:

> [@Thinking through distance matrix calculation](https://discourse.julialang.org/t/thinking-through-distance-matrix-calculation/3725/6):
>
> Note that GPU arrays are tied to the Julia GC, and are freed after they go out of scope on the host, so that might be your problem. That means you need to keep data that is alive on the GPU, alive on the CPU as well. Lastly, because there’s no way for us to indicate GPU memory pressure to the Julia GC, you might need to manually finalize(arr) at some points. I played some more with the example, now also mapping the outer loop into the GPU’s execution model (makes the code cleaner) and introduc…

are still valid in 1.8.2?  
Thanks.  
–shiv–

---

_[View the full topic](https://discourse.julialang.org/t/fast-tile-search/89821)._