 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Having just installed POV-Ray 3.5 on my PowerBook G3, running MacOS
10.1.5, I was a bit surprised to see it using only about 50-70% CPU,
even with nothing else running and the "Friendliness" set to
"Tyrrannical". This seems to be independent of whether Preview is
switched on, or the particular scene file in use.
Is anyone else seeing this?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Jonathan Morton" <chr### [at] chromatix demoncouk> schrieb im Newsbeitrag
news:3D2### [at] chromatixdemoncouk...
> Having just installed POV-Ray 3.5 on my PowerBook G3, running MacOS
> 10.1.5, I was a bit surprised to see it using only about 50-70% CPU,
> even with nothing else running and the "Friendliness" set to
> "Tyrrannical". This seems to be independent of whether Preview is
> switched on, or the particular scene file in use.
>
> Is anyone else seeing this?
This is normal. Under Mac OS X no application may hog the whole CPU.
Thus POV-Ray cannot get as much CPU time as under Mac OS 9. For this
reason the documentation/requirements recommend using Mac OS 9 for
maximum render speed.
Thorsten
____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg
I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>>Having just installed POV-Ray 3.5 on my PowerBook G3, running MacOS
>>10.1.5, I was a bit surprised to see it using only about 50-70% CPU,
>>even with nothing else running and the "Friendliness" set to
>>"Tyrrannical". This seems to be independent of whether Preview is
>>switched on, or the particular scene file in use.
>>
>>Is anyone else seeing this?
>
> This is normal. Under Mac OS X no application may hog the whole CPU.
> Thus POV-Ray cannot get as much CPU time as under Mac OS 9. For this
> reason the documentation/requirements recommend using Mac OS 9 for
> maximum render speed.
I would expect this if other applications were using the CPU, but they
aren't - there's 30-40% CPU completely unused. Other Carbon-based apps
are able to use 100% (or close to that figure) as required.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3D3### [at] chromatixdemoncouk> , Jonathan Morton
<chr### [at] chromatixdemoncouk> wrote:
> I would expect this if other applications were using the CPU, but they
> aren't - there's 30-40% CPU completely unused. Other Carbon-based apps
> are able to use 100% (or close to that figure) as required.
The problem is that rendering is done in a cooperative thread, which means
if that thread takes over the CPU for more than two seconds, POV-Ray will
get blocked by Mac OS X. As it is not predictable how long the next pixel
will take, the proper way to avoid this is to give time to other cooperative
threads after every pixel. This should never be a problem:
Of course, Mac OS X should still automatically return the unused time to
POV-Ray, but it fails to do so. This is a bug in the Mac OS X threading of
Carbon applications, unfortunately :-(
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
