# 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:** 1

<div class="post-metadata">

**Author:** ![bartv](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bartv/32/130052_2.png) [@bartv](https://meta.discourse.org/u/bartv)\
**Post date:** [May 6, 2018, 12:27pm UTC](https://meta.discourse.org/t/huge-server-load-processing-digests-after-import/86874/1 "2018-05-06T12:27:35Z")

</div>

Hi,

after running an import with 300k users, I found that running the weekly digest is a bit of an issue: the server will queue 100k emails at once and processing them is hard on the machine - the load spikes up (about 10x), making the site very slow for a hours. I suppose this is an edge case of running an import - with organic signups these will be distributed more evenly throughout the week, making this less of an issue.

For now, I’ve flushed the email jobs and stopped generating digests, but I’d like to re-enable them.

What’s the recommended strategy for handling this - is there a way to ‘spread out’ the generation of the digests?

---

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