[VoiceOps] Old code vs bold code

Daryl G. Jurbala daryl at introspect.net
Mon Dec 21 14:30:58 EST 2009

I agree that local storage MAY be an issue....but in a call processing box you shouldn't be hitting the disk all that much.  Also, the free version of ESXi supports iSCSI and NFS....so.....I have to go back to people not actually knowing what they are talking about and repeating anecdotes they've read.  And as we all know, it's much easier to find someone spouting off about a problem they are having rather than just checking in to say "everything's fine here".

On Dec 17, 2009, at 9:43 PM, nick hatch wrote:

> Indeed, that makes sense, and is what I was getting at. However, if you have a local datastore, you're generating hardware interrupts on the box above what one would see with remote storage, no? It would seem to make sense that under heavy load, when interrupts matter, not running a RAID controller of your own could be an advantage. Gigabit NICs have sane methods of dealing with interrupts, like coalescence.
> I could be wrong, however. My point was just an attempt to explain why someone might think timing issues are related to "non-enterprise" VMWare.
> -Nick
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops

More information about the VoiceOps mailing list