# Is celery supposed to take up 100% of your CPU every time you publish?

**URL:** <https://discuss.openedx.org/t/is-celery-supposed-to-take-up-100-of-your-cpu-every-time-you-publish/9540>\
**Category:** Site Operators\
**Tags:** nutmeg\
**Created:** [March 9, 2023, 6:02pm UTC](https://discuss.openedx.org/t/is-celery-supposed-to-take-up-100-of-your-cpu-every-time-you-publish/9540 "2023-03-09T18:02:06Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ABC](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/abc/32/4946_2.png) [@ABC](https://discuss.openedx.org/u/ABC)\
**Post date:** [March 9, 2023, 6:02pm UTC](https://discuss.openedx.org/t/is-celery-supposed-to-take-up-100-of-your-cpu-every-time-you-publish/9540/1 "2023-03-09T18:02:06Z")

</div>

I recently noticed that on an Amazon t3a.large (2 VCPUs, 8GB RAM), whenever I hit publish of even a single page, celery spikes both CPUs to effectively 100% (or as much as they can take from other processes.)

I’m just wondering if this is expected, because celery just does a lot of work on publish? (Or whether it’s perhaps related to the [other issue](https://discuss.openedx.org/t/students-progress-page-doesnt-update-when-new-problems-are-added/9470/12) I’m having.)
