Just a reminder that the included scenes\advanced\benchmark.ini/pov file is
diferent from the winpov menu render\run benchmark. The picture looks diferent.

Would be nice to match these up before release.
Added to flyspray bug reporting.

Stephen S

Post a reply to this message

> Just a reminder that the included scenes\advanced\benchmark.ini/pov file is
> diferent from the winpov menu render\run benchmark. The picture looks diferent.
>
> Would be nice to match these up before release.
> Added to flyspray bug reporting.
>
> Stephen S
>
>

It would be good to remove at least one of those lines from benchmark.ini:
Display=Off
This disable the preview.

Output_To_File=Off
This disable saving the resulting image.

As it is now, there is NO preview and the image is NOT saved anywhere.


Alain

Post a reply to this message

On 23/05/2010 7:33 PM, Alain wrote:
>
> It would be good to remove at least one of those lines from benchmark.ini:
> Display=Off
> This disable the preview.
>
> Output_To_File=Off
> This disable saving the resulting image.
>
> As it is now, there is NO preview and the image is NOT saved anywhere.
>
>

There is a "benchmark_Display.ini" which has the settings:

;Buffer_Output=Off
;Buffer_Size=0
Display=On
Output_To_File=On


-- 

Best Regards,
	Stephen

Post a reply to this message

On 23.05.10 20:33, Alain wrote:
> As it is now, there is NO preview and the image is NOT saved anywhere.

That is kind of the point of a processor benchmark and intentional :-)

	Thorsten

Post a reply to this message

Thorsten Froehlich <tho### [at] trfde> wrote:
> On 23.05.10 20:33, Alain wrote:
> > As it is now, there is NO preview and the image is NOT saved anywhere.

> That is kind of the point of a processor benchmark and intentional :-)

  How much overhead would displaying the image cause in reality? After all,
it would be nicer to see the image being rendered instead of just some
percentage...

-- 
                                                          - Warp

Post a reply to this message

On 23/05/2010 8:24 PM, Warp wrote:
> Thorsten Froehlich<tho### [at] trfde>  wrote:
>> On 23.05.10 20:33, Alain wrote:
>>> As it is now, there is NO preview and the image is NOT saved anywhere.
>
>> That is kind of the point of a processor benchmark and intentional :-)
>
>    How much overhead would displaying the image cause in reality? After all,
> it would be nicer to see the image being rendered instead of just some
> percentage...
>

My Intel Core2 Duo 2.20GHz 3 Gig ram, laptop rendered the benchmark in 
39m 40s with benchmark_Display.ini and 17m 56s with benchmark.ini.

Coincidently after a post by Stephen on another forum I checked it. I 
did have other programs running but was not actively using them.

-- 

Best Regards,
	Stephen

Post a reply to this message

On 23.05.10 21:24, Warp wrote:
> Thorsten Froehlich<tho### [at] trfde>  wrote:
>> On 23.05.10 20:33, Alain wrote:
>>> As it is now, there is NO preview and the image is NOT saved anywhere.
>
>> That is kind of the point of a processor benchmark and intentional :-)
>
>    How much overhead would displaying the image cause in reality? After all,
> it would be nicer to see the image being rendered instead of just some
> percentage...

Well, the overhead would not be much indeed. But that isn't the problem. The 
problem is that it cannot be predicted how much overhead it uses, and it 
will depend on the GPU (if any). Running this on a system meant as a server, 
which is usually fast running headless might add bias of a few percent 
consistently even when doing multiple runs...

Or imagine a slow CPU and an X display over an encrypted connection. The 
data transfer could draw so much CPU power...

Or a million of other alternative scenarios that could make the benchmarking 
go wrong...

In short: No display and no disk output simply eliminates two random 
variables from the measurement.

	Thorsten

Post a reply to this message

Am 23.05.2010 20:33, schrieb Alain:

> It would be good to remove at least one of those lines from benchmark.ini:
> Display=Off
> This disable the preview.
>
> Output_To_File=Off
> This disable saving the resulting image.
>
> As it is now, there is NO preview and the image is NOT saved anywhere.

This is by design. The benchmark is /only/ a benchmark of the render 
engine, and any output activity is /not/ part of what it should measure.

Post a reply to this message

Stephen <mca### [at] aolDOTcom> wrote:
....
> There is a "benchmark_Display.ini" which has the settings:
>
> ;Buffer_Output=Off
> ;Buffer_Size=0
> Display=On
> Output_To_File=On
>
>
> --
>
> Best Regards,
>  Stephen

I don't have this file, but that was what I changed.
Note: the internal benchmark lists only 44 total objects, and the benchmark.ini
when run lists about 172 objects. There is also a big difference in photon time.
I don't think this has anything to do with display or saveing files.

Stephen S

Post a reply to this message

Stephen <mca### [at] aoldotcom> wrote:
> My Intel Core2 Duo 2.20GHz 3 Gig ram, laptop rendered the benchmark in 
> 39m 40s with benchmark_Display.ini and 17m 56s with benchmark.ini.

  Displaying the image while rendering slows down rendering speed to half?
I can't believe that. There must be an error somewhere.

-- 
                                                          - Warp

Post a reply to this message