I have a small Omeka 2.3.1 installation running on AWS with 1.7 gigs of memory, with 800mb free . I use the Omeka site for teaching. I recently adjusted the php meomory limit size in Apache2/sites-enabled to 32 mb. I just noticed that thememory limit in etc/php5/apache2/php.ini is 128 mb. I'm not sure which one is actually in effect.
Yesterday I did my first neatline class and had 8 students try to create a neatline exhibit at the same time. The server ground to a halt, and it took a few minutes before I was able to resume. But I continued the workshop as a demo with just me setting up the exhibit.
My question is: does anyone have any experience with tuning the php memory limit for neatline? I'm especially intersted in experience with several simultaneous users.
8 people creating ordinary omeka exhibits works fine.
We've not had great experience with the Small instance on AWS, and after some investigation, we found that the biggest issue was the connections with MySQL and the memory in the process forks. One thing that may help slightly is turning off the spatial querying for the exhibit, but I'm not sure you'll find it satisfactory for multiple, simultaneous use. Linux will fork the main PHP process when dealing with simultaneous requests.
8 users with 128Mb memory allocations (assuming the process forks each user) is 1Gb of memory, and that's before you add in what memory MySQL, Apache, SSH and other daemons need to run. We found pushing database stuff off to RDS improved things exponentially. You may also want to take a look at OpenShift; I've got a quick start that a lot of our grad fellows use for their projects (https://github.com/waynegraham/omeka-quickstart/tree/master).