20K pages, 23Gb: Can Joomla 3.3 handle without any issues?

[hanjimail]

I have been asked by a client with the question above title.

Questions:

1. MySQL capacity in Joomla 3.3?

2. Akeeba Backup can handle that big site with the big db size?

3. site traffic 20k pv / month currently

Server CPU XEON, Main Memory 14Gb, HDD 700Gb

If Joomla 2.5, can it handle without problems?

Norito

[sitesrus]

Yes. Things just bog down as your db gets larger, traffic loads too high, and etc. It's easy to identify bottle knecks though and then remedy either via hardware or software. But joomla is open source and tweaking/hacking isn't a good idea so you will have to focus on hardware solutions probably. And joomla has good developers so I'm sure it's optimized to run on the platform.

[hanjimail]

Thank you for your input.

It seems 28Gb out of 29 may be PDF files, so I have to find ways to back them up smoothly.
It is impossible to get zipped file via FTP to my PC.

[jaymzyates]

28GB of PDF files stored as binary objects in the database or are those files stored on flat file storage somewhere with references to file location in the database? If they are actually in mysql and you have a heavy read commit you are going to want to address that with better hardware.

[itoctopus]

There is virtually no limit when it comes to MySQL. Your website traffic is not that huge, but your number of pages that you have (20,000) means one of the following:

- You'll have to use Joomla's page caching
- You'll have to do some series of optimizing on the actual site (starting with the template, and then the 3rd party extensions, and finally with Joomla's own core)

Your server seems to be more than ample to handle that load - one of our clients has a very similar website with traffic about 1,000,000/month (traffic is spread over 3 websites). You might want to check the case study here:

Code: Select all

 http://www.itoctopus.com/how-we-optimized-a-large-joomla-2-5-website-and-made-it-over-200-times-faster

Note that the post was written a year ago, and since then the traffic and the number of articles have doubled.

I wouldn't trust Akeeba to backup such a website (in fact, I don't trust Akeeba for backing up even tiny websites, but that's a personal opinion), the likelihood that it'll crash is extremely high. If you have cPanel, then you can do the backup from cPanel, which is better and much more stable and supported by your host (so, if something goes wrong, you can tell your host to restore your website from a cPanel backup).

[technicaldk]

It's depend on how many current connection (EP / user online at same time)

[sea2709]

@Hanjimail : Why do you use Joomla 2.5 instead of using Joomla 3.x ?

[droidgig]

If they are actually in mysql and you have a heavy read commit you are going to want to address that with better hardware.

[teo]

If it can help to evaluate, I’m working on a Joomla! 3.3.3 site with 10K contents and 270K page views monthly.
It is running on a VPS with 4 core, 2GB of RAM and SSD storage in FastCGI + APC and work fine. I’m investigating about table indexing in Joomla! to get less full table scan, but even now, from “Pingdom RUM report” I’m getting satisfied users.
I’ve placed large files on server (audio, video and PDF) in Amazon CloudFront, but before moving it, I had about 18GB of data and Akeeba Backup was managing it.