# Extreme belasting/schijf-IO/CPU/geheugengebruik vraag

**URL:** <https://meta.discourse.org/t/extreme-load-disk-io-cpu-memory-usage-question/171097>\
**Category:** Self-hosting\
**Tags:** server-resources\
**Created:** [23 november 2020 om 22:59 UTC](https://meta.discourse.org/t/extreme-load-disk-io-cpu-memory-usage-question/171097 "2020-11-23T22:59:28Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [23 november 2020 om 23:49 UTC](https://meta.discourse.org/t/extreme-load-disk-io-cpu-memory-usage-question/171097/2 "2020-11-23T23:49:51Z")

</div>

> [@ckshen](#):
>
> is there a log where i can tell who’s accessing the site at a given point in time?

Yes, check `/var/discourse/shared/standalone/log/var-log/nginx/access.log`.

> [@ckshen](#):
>
> is there a way to have the crawlers spread out their requests since these are ‘good’ crawlers?

Yes, the `slow down crawler user agents` site setting.

> [@ckshen](#):
>
> will throwing more CPU/ memory at the server help with the situation? I am a bit skeptical about that since CPU/ memory usage didn’t spike. is 80% average memory utilization too high?

Looks like what you had was I/O wait during the 9:40 peak. Increasing RAM may help as more stuff can be kept at cache, but I don’t know if that peak was read or write, as you did cut off the graph legend 🙃.

That said, if you can afford, increasing the droplet size to the next available size will always help.

---

_[View the full topic](https://meta.discourse.org/t/extreme-load-disk-io-cpu-memory-usage-question/171097)._
