There are no hard and fast There are set system requirements for running Avalon, but as you will want to choose your system depending systembased on your collection size , and expected usage, and desired responsiveness.   Below are examples of systems servers running Avalon and simple statistics highlighting their throughput.

Avalon Demo

...

Server

• https://

...

• demo.

...

CPU:  4 cores

RAM: 16 GB RAM

Disk Space: 500 GB Disk

Encoding Time: 

This system uses Indiana University's Adobe Media Server.  

...

• avalonmediasystem.org

• Hosted on AWS
• Main EC2 box: t2.xlarge
• RDS: cache.t3.micro
• ElastiCache: db.t3.micro

Northwestern University Production System 

Northwestern's Pilot Avalon System uses 4 virtual machines (3 VM and 1 hardware): 

...

1. Avalon web application :  4GB RAM, 2 CPU(VM):  
   • CPU: Xeon E5-2640 @ 2.50GHz, 2 cores, 4 threads
   • RAM:  8GB
   • Disk Space: 25GB local storage plus NFS storage
     
2. Fedora, MySQL and the Solr indexer :  4GB RAM, 2 CPUMatterhorn:  4GB RAM, 8 CPU(VM):  
3. Transcoding (Matterhorn) (physical box):  
   • CPU: Xeon E5-2690 v2 @ 3.00GHz 20 cores, 40 threads
   • RAM: 128GB
   • Disk Space: 4TB local storage plus NFS storage
     
4. Adobe Media Server:  4GB RAM, 2 CPU

File Types We Have Tested

1. External campus enterprise streaming server

Indiana University Production System 

1. Avalon web application, Fedora, Solr:  
   • CPU: Intel(R) Xeon(R) CPU E5-2690 v2 @ 3.00GHz
   • RAM:  24GB
   • Disk Space: 40GB local storage plus 250GB NFS storage
     
2. MySQL:  External service
3. Transcoding (physical box):  
   • CPU: Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz, 12 cores, 24 threads
   • RAM: 128GB
   • Disk Space: 12TB
     
4. Wowza Media Server:  External campus enterprise streaming server