Re: [Alchemi-developers] Converting a current Multi-threaded application (single Server) to a grid application running multiple threads per Executor

[Stuart Jenkins]

Thanks Tibor   Makes sense.   Stuart Jenkins ----- Original Message ----- From: Tibor Biro To: alchemi-developers@lists.sourceforge.net Sent: Monday, January 09, 2006 3:29 AM Subject: RE: [Alchemi-developers] Converting a current Multi-threaded application (single Server) to a grid application running multiple threads per Executor Hi Stuart,   An executor will only get one thread to run at any given time. On the other hand you can setup multiple executors in a machine and each executor will get its own thread to execute, take a look here for instructions http://sourceforge.net/mailarchive/message.php?msg_id=13023495   Regards, Tibor   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stuart Jenkins Sent: Saturday, January 07, 2006 8:49 AM To: alchemi-developers@lists.sourceforge.net Subject: [Alchemi-developers] Converting a current Multi-threaded application (single Server) to a grid application running multiple threads per Executor   HI   Am new to this list so apologies if this is already covered somewhere but I cannot find a direct reference in the documentation.   Currently I have an VB .NET application which spawns multiple threads to get through its workload faster. Each thread only uses perhaps 10-15% of CPU time at any one time and I generally have 6 threads running, and due to connecting to multiple external resources (which take time to respond) the threads cannot run faster than they do - hence there are benefits to having the application run multi-threading rather than sequential processing.   The idea of spawning this work out to executer units has obvious advantages as I could use the CPU resources of multiple workstations. However in the grid thread starting examples in the documentation, it appears as though a grid thread is being told to start (which the manager then farms out to an available executer)   Will the manager farm out multiple threads to each executer? or does an executer get one job at a time? If the executer only gets one job/thread at a time then potentially I will not gain as much performance increase as I would like.... unless perhaps the grid thread that gets farmed out starts 6 threads on the executer which means I would have to program it this way.   Any feedback, ideas or pointers in the right direction for documentation greatly received.     Stuart Jenkins -- This email has been verified as Virus free Virus Protection and more available at http://www.plus.net