Actually, consider this, you have 1 server running 10 different instances for 10 different people and as AWS you have to try and be level handed about how you hand out instances on a single node in your cloud cluster...
How do you make sure that instance 1 isnt hogging all the CPU time that instances 9 – 10 need?
This is the nature of a timeshare system... This goes back to AS400s SYS 34’s and 36’s... Don’t get me wrong I think AWS, and cloud computing in general can be great for certain things (store and forward), but do you really want to chance the interruptions in RealTime media streaming where any delay in processing causes missed or dropped packets...
On 11/16/11 9:43 AM, "Michael Picher" <mpicher@gmail.com> wrote:
Hi guys,
Trying to get to the bottom of some conference bridge issues I'm having with running the system in AWS.
We're hearing a bunch of snap-crackle-pops in conference bridges and when I tcpdum on the server itself I see them in the RTP and see RTP timestamp problems.
I've run the following:
timer_test
freeswitch@127.0.0.1@internal> timer_test 120 10
Avg: 120.004ms Total Time: 1200.315ms
2011-11-16 10:25:56.121131 [CONSOLE] mod_commands.c:461 Timer Test: samplecount after init: 1
freeswitch@127.0.0.1@internal> 2011-11-16 10:25:56.219163 [CONSOLE] mod_commands.c:466 Timer Test: samplecount after first step: 2
2011-11-16 10:25:56.339195 [CONSOLE] mod_commands.c:475 Timer Test: 1 sleep 120 120006
2011-11-16 10:25:56.459259 [CONSOLE] mod_commands.c:475 Timer Test: 2 sleep 120 120040
2011-11-16 10:25:56.579259 [CONSOLE] mod_commands.c:475 Timer Test: 3 sleep 120 119976
2011-11-16 10:25:56.699291 [CONSOLE] mod_commands.c:475 Timer Test: 4 sleep 120 120007
2011-11-16 10:25:56.819318 [CONSOLE] mod_commands.c:475 Timer Test: 5 sleep 120 120001
2011-11-16 10:25:56.939375 [CONSOLE] mod_commands.c:475 Timer Test: 6 sleep 120 120031
2011-11-16 10:25:57.059397 [CONSOLE] mod_commands.c:475 Timer Test: 7 sleep 120 119996
2011-11-16 10:25:57.179422 [CONSOLE] mod_commands.c:475 Timer Test: 8 sleep 120 119994
2011-11-16 10:25:57.299461 [CONSOLE] mod_commands.c:475 Timer Test: 9 sleep 120 120005
2011-11-16 10:25:57.419478 [CONSOLE] mod_commands.c:475 Timer Test: 10 sleep 120 119991
test_time
freeswitch@127.0.0.1@internal> time_test 600 10
test 1 sleep 600 1592
test 2 sleep 600 986
test 3 sleep 600 1018
test 4 sleep 600 980
test 5 sleep 600 1005
test 6 sleep 600 1000
test 7 sleep 600 972
test 8 sleep 600 990
test 9 sleep 600 1006
test 10 sleep 600 994
avg 1054
For kernel:
[root@openuc bin]# uname -r
2.6.21.7-2.fc8xen
CONFIG_HZ:
[root@openuc bin]# grep CONFIG_HZ /boot/config-*
/boot/config-2.6.16.33-xenU-x86_64:CONFIG_HZ_100=y
/boot/config-2.6.16.33-xenU-x86_64:# CONFIG_HZ_250 is not set
/boot/config-2.6.16.33-xenU-x86_64:# CONFIG_HZ_1000 is not set
/boot/config-2.6.16.33-xenU-x86_64:CONFIG_HZ=100
/boot/config-2.6.18-164.15.1.el5.centos.plus:# CONFIG_HZ_100 is not set
/boot/config-2.6.18-164.15.1.el5.centos.plus:# CONFIG_HZ_250 is not set
/boot/config-2.6.18-164.15.1.el5.centos.plus:CONFIG_HZ_1000=y
/boot/config-2.6.18-164.15.1.el5.centos.plus:CONFIG_HZ=1000
/boot/config-2.6.21-2952.fc8xen:# CONFIG_HZ_100 is not set
/boot/config-2.6.21-2952.fc8xen:# CONFIG_HZ_250 is not set
/boot/config-2.6.21-2952.fc8xen:# CONFIG_HZ_300 is not set
/boot/config-2.6.21-2952.fc8xen:CONFIG_HZ_1000=y
/boot/config-2.6.21-2952.fc8xen:CONFIG_HZ=1000
are the xenU kernel settings screwing me here?
Thanks,
Mike