Support

Akeeba Backup for Joomla!

#38926 Server limitation: I/O usage resources limit reached

Posted in ‘Akeeba Backup for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
3.10.11
PHP version
7.4
Akeeba Backup version
8.2.2 Pro

Latest post by [email protected] on Thursday, 04 May 2023 02:56 CDT

[email protected]

Hello,

Following documents https://www.akeeba.com/documentation/akeeba-backup-documentation/configuration.html and https://www.akeeba.com/documentation/troubleshooter/abwpbackup.html I have done Akeeba configuration as you can see in snap4.jpg. Taking backup server reaches i/o limit, and the site runs slower 24h.

Please, how can we adjust Akeeba in this situation?

Thanks,

Jose Luis Martinez

 

nicholas
Akeeba Staff
Manager

The 10MB/sec limit is way too low to be practical. That was the transfer rate of hard disks 30 years ago.

We could set completely unrealistic time limits in the Fine Tuning section of the Configuration page for your backup profile such as:

  • Maximum execution time: 1 second
  • Minimum execution time: 5 seconds
  • Runtime bias: 50%

This tells Akeeba Backup to work for about half to one second, then sit there for 4 to 4.5 seconds doing nothing. Instead of 15 minutes your backup should now take about an hour and a half. It this still triggers your hosting limits, set the minimum execution time to 10 seconds. Your backup should then take three to five hours.

If that's still a problem, look, my friend, your host is ripping you off. This is the first time in 15 years I have seen a host with data transfer per second limits. This was used 20 to 15 years ago when servers where using a single spinning hard drive which had very limited data throughput (thing low dozens of MiB/sec). The past 15 or so years the cost of storage fell precipitously. Servers started using multiple SAS hard disks (with throughput up to 250MiB/sec), then SSDs (throughput up to several hundreds MiB/sec), then NVMe storage (throughput in the several thousands MiB/sec), then SANs (throughput of many thousands MiB/sec, practically limited only by the physical network interface and logical network stack performance). That is to say, there has been no practical reason for a server to limit data read/write. I'd recommend moving your site to a decent host. Rochen costs under 13 Euros a month and does not have these silly limits. Papaki.com costs half as much, it has no limits, it's just less features in the basic package (no SFTP, 7GiB of storage) than Rochen. Both are very solid hosts I have used myself, both offer WordPress-optimised servers.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

[email protected]

Hello Nicholas:

Thanks a lot for your reply. With new settings backup takes 1h 40s and i/o resources never exceed 10%. Unfortunately server limitation appear again due 90s HTTP Query as you can see in the image.

Migrating server is not possible now, but is a must for this summer.

Regards,

José L. Martinez

nicholas
Akeeba Staff
Manager

Why do you have a 90 seconds request? It does not make sense. Each request will take about 5 seconds; that's what we configured.

The only requests which might take longer are those where your archive is being uploaded to Google Drive. 

However, I saw in your previous log file that you had enabled chunked uploading with a chunk size of 10MiB (default), which means that your 1.18 GiB backup is being uploaded one small chunk at a time. I see that each chunk took about a second to be uploaded.

The only reason I can think of this long HTTP request, without having a new log file, is that something got stuck while uploading. You could try increasing the chunk size up to 50 MiB and see if that helps. Beyond that, there's really not much else you can do beyond using a different server.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

[email protected]

You're right, the archive is being uploaded to Google Drive. We will disable temporarily cron job and Google Drive upload, launching backups only from console where configuration parameters take effect.

Thanks again,

Regards,

José Luis Martínez

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!