# GPU performance problem of locally connected layer with Tullio

**URL:** <https://discourse.julialang.org/t/gpu-performance-problem-of-locally-connected-layer-with-tullio/85469>\
**Category:** Machine Learning\
**Tags:** tullio\
**Created:** [August 8, 2022, 11:36am UTC](https://discourse.julialang.org/t/gpu-performance-problem-of-locally-connected-layer-with-tullio/85469 "2022-08-08T11:36:08Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![johnbb](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/johnbb/32/34233_2.png) [@johnbb](https://discourse.julialang.org/u/johnbb)\
**Post date:** [August 18, 2022, 9:08am UTC](https://discourse.julialang.org/t/gpu-performance-problem-of-locally-connected-layer-with-tullio/85469/2 "2022-08-18T09:08:31Z")

</div>

Have you considered `@ein`? In a brief test, I found that `@ein` was faster than `@tullio` on GPU with a 1×1 filter, please see [here](https://discourse.julialang.org/t/flux-locally-connected-layer-performance/55711). Would be great to a fast locally connected layer in Flux.

---

_[View the full topic](https://discourse.julialang.org/t/gpu-performance-problem-of-locally-connected-layer-with-tullio/85469)._