Queueing Windows processes

  • Thread starter Thread starter verm25
  • Start date Start date
V

verm25

Let's say I start twenty roughly identical processes (same code running
analysis over same sized data). I want to queue these processes once
they
are started (I need to do GUI config for each process so I cannot
script
starting the processes in a queue). Basically I want a piece of
software,
where I can select PIDs and it will only let one process run until it
finishes (my processes do not die unless I kill them so finishes means
that analysis is done, i.e. CPU usage falls below some threshold).
I find Windows to be terrible at multitasking so queueing by hand I get
twice faster analysis than if all processes constantly switch CPU
access. Hence, is there software that automates queueing for running
processes?
 
Let's say I start twenty roughly identical processes (same code running
analysis over same sized data). I want to queue these processes once
they
are started (I need to do GUI config for each process so I cannot
script
starting the processes in a queue). Basically I want a piece of
software,
where I can select PIDs and it will only let one process run until it
finishes (my processes do not die unless I kill them so finishes means
that analysis is done, i.e. CPU usage falls below some threshold).
I find Windows to be terrible at multitasking so queueing by hand I get
twice faster analysis than if all processes constantly switch CPU
access. Hence, is there software that automates queueing for running
processes?
Click to expand...

It seems that you are currently using a GUI to launch several jobs,
and that you then wish to intercept these jobs and release them for
execution one by one.

This can easily be achieved with a batch file if you modify your
interface so that it becomes command-line driven instead of
GUI-driven.
 
Well, you sort of kind of understand my problem, but the
bad news is that your solution is not possible for me.
My jobs are filters written for a larger program (actually free
software but too big for me to rewrite my way), so I have to
start twenty instances of the big program, configure my filter
for each instance, then let it go. This is why my processes do
not die in the end - the big program keeps running even though
the filter is done.
So given the problem and given that the obvious solution is
too hard to implement, any suggestions?
 
Well, you sort of kind of understand my problem, but the
bad news is that your solution is not possible for me.
My jobs are filters written for a larger program (actually free
software but too big for me to rewrite my way), so I have to
start twenty instances of the big program, configure my filter
for each instance, then let it go. This is why my processes do
not die in the end - the big program keeps running even though
the filter is done.
So given the problem and given that the obvious solution is
too hard to implement, any suggestions?
Click to expand...

A crude solution would be for the larger program to monitor
a semaphore file: It will pause until such time as the semaphore
file exists.
 
Back
Top