skrul

Hey follks, if you are interested in running a Jamulus server on AWS I put up some public EC2 AMIs of Ubuntu 18.04 running Jamulus 3.5.0. All you should need to do is launch an instance from the AMI in the region you want (I've been using m3.small) and make sure you add the "All UDP / Anywhere" rule to the security group before launching. Edit: I've updated all regions with Jamulus 3.6.2 Please let me know if you find this useful! I copied the AMIs to all of the US regions, let me know if you need...

This is done! Search the community AMIs for "Jamulus" and you will find it. I'll update the post above as well.

I think our setups are pretty similar -- I am also using buster and don't have anything else running except for jamulus and telegraf for metrics collection. My systemd startup script is based on https://jamulus.io/wiki/Server-Linux. I am not using multithreaded mode. I did disable the GUI mode of the OS but that's about all the changes I made from a stock install. Attached are some CPU graphs of cpu mean and each individual cpu. Mean stayed below 15% the individual CPUs peaked at around 30%.

Just wanted to share a recent experience using a Raspberry Pi 4 as a server. In the past I've been using AWS to host our Jamulus jams, but I wanted to try hosting a server at home since I have fiber internet. I set up my Raspberry Pi 4 (4 GB) with standard Raspberry Pi OS and built Jamulus from the github source. We did a jam with 8 people and it worked flawlessly. During the jam the CPU usage never went above 17% and was transferring about 6 Mb/s for a few hours. Nice work everybody :)

Recently I've been using a t3.small instance with dedicated tenancy and it has been rock solid for jams with 8 or 10 folks. I noticed a significant difference between using the same instance type with default tenancy. Note that the dedicated tenancy is expensive - you get charged $2 every hour if you have one or more dedicated instances running. For this reason I start the server when we start playing and try to remember to stop it when we are done!

Hey kieran, I haven't tried this in a while but I recall using something like this to play an mp3 through Jamulus: alsaplayer -o jack -d "Jamulus:input left,Jamulus:input right" Good luck!

FYI I've been uploading Jamulus AMIs to all of the US AWS regions. To launch your own private server, just search the Community AMIs for "jamulus" and choose it, then choose your instance type (I've been using t3.small). Next you need to make sure you open up UDP to the world so go to security groups and add a rule with type "All UDP" with source "Anywhere". Launch the instance and Jamulus will start up automatically :)

This sounds great! Would love to hear more about your server setup. I've been building and publishing AMIs with Jamulus pre-installed and I've been wondering if using a low-latency kernel would make a difference. Did you try any other instance types? I've been using t3.small which seems to handle it well, we had around 8 players and it didn't seem to use too much CPU/network. Next time I want to try using one of the dedicated instances.