It's not just the memory consumption you have to watch out for. Since each vblade process opens a raw socket then that means for every packet received there's a copy to memory and a context switch done to wake up each and every one of those vblade processes.
I'd consider vblade a reference implementation and nothing more. After 3-4 vblade processes, something like qaoed (which is multithreaded and opens a single raw socket) is much more efficient. You can score the qaoed source on google code. I don't have an exact url with me right now. Good luck, -kelsey -- Kelsey Hudson Sr. Systems Administrator, DrJays.com 888.437.5297 x 134 (desk) 619.852.6374 (cell) -----Original Message----- From: "Leandro Anthonioz" <[EMAIL PROTECTED]> Date: Thu, 4 Dec 2008 11:40:32 To: <aoetools-discuss@lists.sourceforge.net> Subject: [Aoetools-discuss] vblade processes memory consumption ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Aoetools-discuss mailing list Aoetools-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/aoetools-discuss
