I have set up a large Joomla website (5,000 articles) on an AWS m1.small instance as a test for her site. The m1.small has 1.67GB of memory and we're hoping that her site will load a little faster. We are using the EBS-backed, 64-bit Ubuntu 12.x Bitnami LAMP AMI in US-WEST-2 (Oregon) with just the MySQL that's on the instance. I copied her Joomla installation over, I didn't use the Joomla Bitnami stack because Joomla is not installed in the Apache server root (which drives me crazy, by the way).
The site seems faster than just her standard shared web hosting site, but when my client tries to work in the Joomla administrative panel, clicking on something results in a spinning cursor followed by an empty browser, as thought it didn't wait long enough to load the contents.
I really don't want to give up on this scenario (since I had planned it for myself) but this repeated timeout on simple loading of admin pages is unacceptable. The CloudWatch stats show that we're barely using the full power of that CPU. I don't see anywhere that I can track MEMORY usage to see if we're maxing out the server memory: I seriously doubt it.
Are there any settings that I can tweak to prevent this repeated timeout of page loading?
Thanks,
Toolie