Site Restoration

#34220 Kickstart extraction fails on Amazon EFS server

Posted in ‘Site restoration’
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

PHP version
CMS Type
CMS Version
Backup Tool Version
Kickstart version

Latest post by nicholas on Monday, 14 December 2020 10:03 CST


Migrating Joomla sites from AWS server to AWS EFS server. Benchmarking a single site reveals that current AWS server extracts files in 11 -15 seconds. AWS EFS server takes over 30 minutes to extract the same 345,654.031 JPA file.

I was able to eventually extract and install two sites. The third site stopped extracting with no apparent error. Debug.txt is attached. Total number of sites to migrate is fifteen. AWS EFS is supposed to be an elastic environment that adjusts as directory volume grows, but it appears that I am hitting a disk space ot time out issue and kickstart is not anticipating the expanding environment.  

Has anybody reported a similar issue and are there any server configurations that need to be  made?

Akeeba Staff

Benchmarking a single site reveals that current AWS server extracts files in 11 -15 seconds. AWS EFS server takes over 30 minutes to extract the same 345,654.031 JPA file.

So, AWS EFS is slow as hell is what you're telling me. Namely, 99.94% slower. In other words it is unsuitable for the task at hand.

Using basic common sense will tell you why. Kickstart needs to read stuff from the backup archive and write it to the disk. However, you went from a fast SSD to something the speed of a slow floppy drive from the early 1980s (and yes, I'm old enough to have used the real article). This means that everything takes much, MUCH longer to run. PHP has a time limit. Therefore you will probably reach it, even though Kickstart is actively trying to minimize that possibility. It will reach it because even writing 64Kb might take several minutes due to the elasticity of the storage's avaialbility.

Clearly, AWS EFS is not the right thing to use for this task. It has unreliable performance characteristics. It is overall slow. It is great for long term, infrequently accessed storage with relatively speedy sequential read. Like S3. In fact, it's BECAUSE it uses S3 under the hood that has these characteristics! It's NOT suitable for your site's files. That's why Amazon also has EBS which is high performance, elastic block storage. What you need is EBS not EFS. 

In any case I am closing your ticket because it falls under the category of hosting issue which is outside our control.

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!

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!