# \[Screencast\] Improving Partial Loading Performance

**URL:** <https://metaruby.com/t/screencast-improving-partial-loading-performance/1854>\
**Category:** Learning Ruby\
**Created:** [August 6, 2018, 11:36am UTC](https://metaruby.com/t/screencast-improving-partial-loading-performance/1854 "2018-08-06T11:36:01Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![kobaltz](https://metaruby.com/user_avatar/metaruby.com/kobaltz/32/982_2.png) [@kobaltz](https://metaruby.com/u/kobaltz)\
**Post date:** [August 6, 2018, 11:36am UTC](https://metaruby.com/t/screencast-improving-partial-loading-performance/1854/1 "2018-08-06T11:36:01Z")

</div>

N+1 queries can make an application slow. Having queries called within views can also slow down an app as well as making it less extendable. [https://www.driftingruby.com/episodes/improving-partial-loading-performance](https://www.driftingruby.com/episodes/improving-partial-loading-performance?utm_medium=social&utm_campaign=weekly_episode&utm_source=metaruby)

> **[Episode 145 - Improving Partial Loading Performance | Drifting Ruby](https://www.driftingruby.com/episodes/improving-partial-loading-performance?utm_medium=social&utm_campaign=weekly_episode&utm_source=metaruby)**
>
> N+1 queries can make an application slow. Having queries called within views can also slow down an app as well as making it less extendable.