>> Currently I am compiling the basic x86 system from the developement >> enviroment and we will use that till I can build an x86_64 optimized build. > >There probably won't be a huge benefit to doing a 64bit build.
Actually Opterons are very good at doing fast fourier transforms, when the code is optimized for them, which are done frequently in various asterisk operations. Also Opeterons operating in 64 bit mode are close to twice as fast at doing memory transfers (something about a bus twice as wide might have something to do with it) which asterisk does frequently as well. This is why they are used in large clusters most of the time. These systems are being built to sneak out every single last call possible. >> Also how hard is it to get the development enviroment to use the head >> version of asterisk instead of the stable... I realize that some of the >> patches might need to be updated but besides that. The reason I ask is >> we found some bugs in asterisk and are patching the head to fix them. > >I would be against this most of the time. head isn't always stable. It >shouldn't be too difficult to create two asterisk packages, one from >stable, one where you could specifiy a version number from svn (or >something along those lines). I realize that running head is not always a good idea and basically I was going to create a patch for the build config file to do this (as I do not think it is necessary to have a second package). Some of the people at my office are fixing the bugs in asterisk and submitting patches for them as they run across them. More over fixing bugs in the interface libraries to asterisk.
<<winmail.dat>>
_______________________________________________ Astlinux-users mailing list [email protected] http://lists.kriscompanies.com/mailman/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
