On Fri, Jun 18, 2010 at 9:58 PM, Martin Steinmann <[email protected]> wrote: >> >> >>Woof! >> >>On Fri, 18 Jun 2010 16:07:42 -0400, M. Ranganathan <[email protected]> >>wrote: >> >>> It should be pretty easy to implement this. Any opinions? >> >>Please measure the system load while 1000 simultaneous zip/unzip >>operations are running in 1000 different threads. > > So how does the math work here? I recall that Nortel used to sell systems > with up to 10,000 mailboxes on CallPilot with 96 ports. If you assume that > at least half the calls into VM are to listen to messages and not record new > ones and if you assume that the 96 ports are dimensioned for peak load, then > <50 sessions need to be processed at any one time. 50 parallel sessions > compressing mp3 might still be a lot, but it's better than 1,000. Now go > back and think about SMB :) > >> >>If you are comfortable that this load will not effect the ability to >>handle calls, then by all means go for it. >> >>Of course, perhaps the new management has some more realistic views than >>the previous management over how many simultaneous IVR calls the system is > >>actually expected to handle. ;-) > > > ...and I keep thinking of that system Woof always told us about that he was > involved with that had this phenomenal media processing capacity :). We have > some ways to go optimizing performance (or buy larger CPUs). > --martin > >> >>But currently storage space is way cheaper than CPU cycles, so what is >>driving this request? >> >>--Woof! > > > _______________________________________________ > sipx-dev mailing list [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev > sipXecs IP PBX -- http://www.sipfoundry.org/ > Most traditional TDM based "port" VM systems stored in raw PCM format, which was "ridiculously" small in file size. Then again it was an analog recording not sampled at over 8 or 9.6k, and the ability to play the file over the handset was being transcoded by an independent hardware device. A really cool system we used to install (including interfacing directly to Nortel DMS100 switches) had the ability to download to PC (back in DIALUP DAYS) as PCM and convert to WAV in its own player (and had gateways to Lotus, Exchange/GroupWise for true email/voicemail sync as a unified inbox).
There's a trade off here of disk space, storing recordings, zipping them for storage, etc. Or simply taking the plunge and encoding them as MP3 which has long term benefits and not having to do all of the other items to deal with storage, download times, etc. I'm biased on this issue. I feel strongly about it, but that's because I feel the format is truly "more portable". Where do you burn the cycles? Not on the server, but on every device that uses the WAV file outside of it? Or do you make the server do extra encoding/decoding when it is used directly but make it faster, easier for "a''L other devices that touch it. I have sipxconfigUI but can only "play" the WAV file in Firefox. It won't play in IE, nor chrome, etc. Times are a changing... _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
