On Fri, Feb 18, 2011 at 03:27:35PM +0100, Adi Kriegisch spake thusly: > vblade kind of a reference implementation. Starting multiple vblade > processes will not help either because it will just eat up available iops > be introducing unnecessary, uncoordinated reads and writes. When talking
Wouldn't the block layer aggregate and coordinate these reads and writes? vblade is just reading/writing from a file like any other process, no? I find vblade performance to be pretty decent. Especially since the "thundering herd" problem of all vblade processes being awakened by every packet was solved. I am never limited by CPU and very rarely even network, only by disk performance itself. -- Tracy Reed Digital signature attached for your safety. Copilotco Professionally Managed PCI Compliant Secure Hosting 866-MY-COPILOT x101 http://copilotco.com
pgpkA8eDziZgq.pgp
Description: PGP signature
------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________ Aoetools-discuss mailing list Aoetools-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/aoetools-discuss
