Thanks - I've been following the architecture changes for awhile and it's great to see what they will be able to do.
On Jul 7, 2012, at 19:03 , Josh Patten wrote: > Don't forget that in 4.6 the media components can now be assigned to a server > other than the primary server. So you can run non-media components in VM, > such as your config server and enjoy the benefits of using a VM, like > snapshotting. > > Food for thought... > > On Sat, Jul 7, 2012 at 5:16 PM, Kurt Albershardt <k...@nv.net> wrote: > I completely forgot about the FS component and all of its potential media > I/O. That helps with architecture, and what to look for as we tune the VM. > I think it should work OK for this application, as there should be very > little of that kind of traffic. > > thanks~ > > > > On Jul 7, 2012, at 16:08 , Tony Graziano wrote: > > > I think it really depends on the speed and load of your storage system. > > > > Contrary to what you think, the bigger concern is not media streams, > > but when the media streams are played or recorded or anchored to the > > server and shared: auto attendant, voicemail, conference server. > > > > So the big concern here is the media server (Freeswitch). > > > > So besides the necessary precautions for the kernel and timing, the > > storage subsystem and its expected load. A small server with half a > > dozen users would not notice it. Get a few conference calls going and > > its a different picture. > > > > On Sat, Jul 7, 2012 at 5:38 PM, Kurt Albershardt <k...@nv.net> wrote: > >>> From http://wiki.sipfoundry.org/display/sipXecs/Hardware+Requirements > >> Production systems are not recommended to run on Virtual Servers due to > >> the manner in which the CPU is shared. Timing is critical to voice codecs > >> and virtualization creates problems in production systems. > >> > >> I'm guessing this is primarily a concern for media streams (sipXbridge) > >> but is SIP itself that sensitive to microseconds? > >> > >> I'm installing 0.0.4.5.2 under container virtualization (OpenVZ via > >> Proxmox) and wondering what I should expect. > >> > >> > >> --thanks
_______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
