# \[Screencast\] Working with Large Data

**URL:** <https://metaruby.com/t/screencast-working-with-large-data/2265>\
**Category:** Learning Ruby\
**Created:** [August 5, 2019, 11:54am UTC](https://metaruby.com/t/screencast-working-with-large-data/2265 "2019-08-05T11:54:36Z")\
**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 5, 2019, 11:54am UTC](https://metaruby.com/t/screencast-working-with-large-data/2265/1 "2019-08-05T11:54:37Z")

</div>

When database tables get large, things can slow down significantly. In this episode, we look at a few things which helps keep databases performant and the client side responsive. [https://www.driftingruby.com/episodes/working-with-large-data](https://www.driftingruby.com/episodes/working-with-large-data?utm_medium=social&utm_campaign=weekly_episode&utm_source=metaruby)

> **[Episode 201 - Working with Large Data | Drifting Ruby](https://www.driftingruby.com/episodes/working-with-large-data?utm_medium=social&utm_campaign=weekly_episode&utm_source=metaruby)**
>
> When database tables get large, things can slow down significantly. In this episode, we look at a few things which helps keep databases performant and the client side responsive.