Hi,

how about a client/server aproach? A sort of daemon running in the backgroup
which is connecting to the GUI via TCP/IP (local or remote RPC).
The GUI does "only" dispatching of the source to all "known" daemons.
Animations with tons of images could be created much faster.
If you have a dual CPU system, you "simply" run two daemons and set the
affinity to a dedicated CPU. The GUI would still communicate through TCP/IP via
localhost (loopback).
This would also be very nice for Winows GUI plus a couple of Linux/UNIX boxes
with "just" daemons running on it!
If you "spin" this idea a little bit further, you could imagine that you could
use other people's CPUs over the net (if they allow it). There are a lot of
linux/unix boxes running 24x7 and ideling most of the time.

I'm aware that this is definitly not something that can be realized easily. But
as a more general direction it would be very nice.

regards,
Peter

Jack schrieb:

> Hi:
>
> I am running win2k with dual pIII 800Mhz.
>
> My kernal is setup for dual processing (I have other applications that
> utilize the dual PIIIs).
>
> I am running a patch of megaPOV0.7, called POVMan 0.71.4.
>
> It does not seem to be utilizing the dual CPUs.
>
> Is this the nature of the application or is there a setting I am not using?
>
> Best regards,
> Jack

Post a reply to this message