🚀 go-pugleaf

Alberto wrote:

>> What you are asking doesn't really make sense.
>> If there is nothing else running, then you will get 100% of the CPU.
>> OTOH if your programm is running twice, you will get 50%.
>
>It makes a perfect sense. The program is driven by external interrupts.

Ok, so now all of a sudden, we're working under interrupts.
What kind of interrupts are they? Are they hardware interrupts, or do
you have a program running, looking at a port, that then calls the
filter?
DOS style hardware interrupts can do their job before releasing their
lock on the cpu. That job should be as short as possible.

A different approach would be for the interrupt to quickly schedule a
task (FIFO stack) which a task thread would be working on to keep
empty. If the task thread finds there is more work to do when it
finishes the current task, it drops it's quality before starting the
next task. If it has to wait very long before the next task comes
along, it raises the quality before processing it.
Note that this also adjusts for different CPU speeds.

Windows will take care of the rest of the load balancing.
It will suspend your task thread so other programs can run.
When the thread returns, it will find some stacked work, and speed up
to plow through it.