# Huge server load processing digests after import

**URL:** <https://meta.discourse.org/t/huge-server-load-processing-digests-after-import/86874>\
**Category:** Product Support\
**Tags:** activity-summary\
**Created:** [May 6, 2018, 12:27pm UTC](https://meta.discourse.org/t/huge-server-load-processing-digests-after-import/86874 "2018-05-06T12:27:35Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)\
**Post date:** [May 7, 2018, 3:24pm UTC](https://meta.discourse.org/t/huge-server-load-processing-digests-after-import/86874/3 "2018-05-07T15:24:04Z")

</div>

Exactly this, also if your import data didn’t had an explicit field for `last_seen_at`, you should update with it with the timestamp of their last post.

This way, a lot of those 300k users will not get the digest, because the date will be greater than `suppress digest email after days`.

---

_[View the full topic](https://meta.discourse.org/t/huge-server-load-processing-digests-after-import/86874)._