Hi ehmdjii

1. With 166% means that the second CPU does not bring 100% biut 66%?

If so, thats really good result for hyperthreading.

2. There is a "comon used ini-file". Just click on the button "open shared
ini". This "ini" is appended to all renderjobs, so you can influence them.

3. Doku ... I am still searching for someone to write that. :-)

4. The channels. Waiting for Renderjobs to get ready uses CPU-time. The
SMPOV-Main Programm must always look if the renderagents are ready - to put
things togther after all.

The channels say: how many of the Renderjobs "in the SMPOV Que" are "sent
out" and are "watched for beeing ready". This is mostly intresting if you
distribute FULL Scenes (no tiling) AND if you have a LOT of CPU's (more then
8).

The more channels you open, the more CPU-Power MAY BE used, however the more
renderagents can simultaneous be used. If you have less then 8 CPU's (local
or in the network) dont worry about the "Channels".

If you (or anyone) have questions or you plan to write a doku, just sent me
a mail, I would support that :-).


--Theo
-----------------------------------------------------------------------
Distributed Network-Rendering or Local SMP-Rendering. With SMPOV and
POV-Ray 3.5. * Download free at: http://www.it-berater.org/smpov.htm



"ehmdjii" <ehm### [at] SPAMgmxnet> schrieb im Newsbeitrag
news:Xns### [at] 204213191226...
> > I'd like to know if someone has tried something like this with
> > "Hyperthreading" and can report if rendering shows a significant
> > speedup or not. I assume it should be less, then with two real CPU's
> > IF POV-Ray keeps the FPU's busy.
>
> hello,
>
> yes, i have tried it on a P4 3.06 GHz
> and i get about 166% of the "normal" time.
> it varies very much depending on what image i render.
> maybe i can post some testings with optics.pov...
> also, it depends very much on how you tile the image.
>
> your tool is really great, though i think it misses some little features
> like for example a full command line. how could i ever use +am2? :-)
>
> and what about a documentation?
> what is the channel output for?
>
> thanks,
> ehmdjii

Post a reply to this message