Title: High CPU usage
Last modified: August 20, 2016

---

# High CPU usage

 *  Resolved [funsail](https://wordpress.org/support/users/funsail/)
 * (@funsail)
 * [13 years, 4 months ago](https://wordpress.org/support/topic/high-cpu-usage-4/)
 * I start backups on a 400MB site. It takes 6hrs to complete even though most files
   were backed up b4. Mem used 38MB. But CPU uses everything I’m allocated and my
   site is knocked offline err 500.
 * [http://wordpress.org/extend/plugins/wordpress-backup-to-dropbox/](http://wordpress.org/extend/plugins/wordpress-backup-to-dropbox/)

Viewing 2 replies - 1 through 2 (of 2 total)

 *  [davidrab](https://wordpress.org/support/users/davidrab/)
 * (@davidrab)
 * [13 years, 4 months ago](https://wordpress.org/support/topic/high-cpu-usage-4/#post-3448301)
 * Can you increase the memory that is allocated to the site?
 *  Thread Starter [funsail](https://wordpress.org/support/users/funsail/)
 * (@funsail)
 * [13 years, 4 months ago](https://wordpress.org/support/topic/high-cpu-usage-4/#post-3448302)
 * I allocated 128 so it’s not actually using it all.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘High CPU usage’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/wordpress-backup-to-dropbox_ffffff.
   svg)
 * [WordPress Backup to Dropbox](https://wordpress.org/plugins/wordpress-backup-to-dropbox/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wordpress-backup-to-dropbox/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wordpress-backup-to-dropbox/)
 * [Active Topics](https://wordpress.org/support/plugin/wordpress-backup-to-dropbox/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wordpress-backup-to-dropbox/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wordpress-backup-to-dropbox/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [funsail](https://wordpress.org/support/users/funsail/)
 * Last activity: [13 years, 4 months ago](https://wordpress.org/support/topic/high-cpu-usage-4/#post-3448302)
 * Status: resolved