As containers use LXC (a form of "jail" or "openvz like") to run a program on the only kernel that is running on the actual hardware ( instead of mimicking a machine and running a kernel ), FreeSWITCH will probably behave well, if it is the only program running on the actual hardware.

If on the same hardware other programs (containers) are running, you will have exactly the same drawback than running FS on an hardware machine that is running other programs too: contentions of resources, IRQs, timers, kernel structures, etc (eg, a no-no, under high loads).

So, containers are better than virtualization (as in KVM, VMWare, etc), but nothing will beat FS running alone in an actual hardware (containerized or not) for obvious reasons.

Test test test, your use case may be particular and uniq.

-giovanni

On 15 October 2016 at 19:16, Ehsan Minachi <ehsanminachi@gmail.com> wrote:
Hello all,

We’ve containerized our infrastructure. The only piece left is FreeSWITCH which we’re hesitant. Has anyone run FreeSWITCH under high load in a container? Would love to hear if there are any downsides to running FreeSWITCH in a container.

Thank you,

- Ehsan
_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://confluence.freeswitch.org
http://www.cluecon.com

FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org



--
Sincerely,

Giovanni Maruzzelli
Cell : +39-347-2665618