 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Btw, I haven't stopped in for a while, but it's good to see so many familiar
names :)
Phenom II x4 running @2.6gHz
A few isosurfaces, some reflection / transparency, emitting media and
radiosity...
40pps :(
Of course, when I started using POV I got 3-4pps on a scene with just a few
spheres ;)
(I realize this post is dangerously close to being off-off-topic, but it's more
a general observation than a question or anything).
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 6/19/2011 2:00, Chambers wrote:
> 40pps :(
The biggest (to me) unexpected slow-down was when I had something casting
shadows that had a much-too-large bounding box, so every pixel was testing
every light source for every shadow.
--
Darren New, San Diego CA, USA (PST)
"Coding without comments is like
driving without turn signals."
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Darren New <dne### [at] san rrcom> wrote:
> On 6/19/2011 2:00, Chambers wrote:
> > 40pps :(
>
> The biggest (to me) unexpected slow-down was when I had something casting
> shadows that had a much-too-large bounding box, so every pixel was testing
> every light source for every shadow.
Well, I left it running overnight, and it hasn't finished the second radiosity
pass yet, so it's time to do some major optimizing - splitting the isosurfaces
into sections, tightening the bounding boxes, etc. Unfortunately, I can't do
much with the functions - in fact, one of the functions is already a
simplification, and needs to be a bit more complex to get the surface I want.
If I come up with something specific I need help with I'll post in the general
group for some ideas :)
On another note, remember what an annoyingly faithful proselytizer I used to be?
I'm now atheist. It took me a long time to admit it, but what people were
saying they believed didn't line up with what I actually saw happening in life.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 19/06/2011 06:42 PM, Darren New wrote:
> On 6/19/2011 2:00, Chambers wrote:
>> 40pps :(
>
> The biggest (to me) unexpected slow-down was when I had something
> casting shadows that had a much-too-large bounding box, so every pixel
> was testing every light source for every shadow.
For me, it was when I tried to build a volumetric photon map.
I had a render which took 20 minutes or so. Turned on scattering media
and volumetric photon maps, and now the photon map alone takes 45
minutes to build. The actual render slowed to something absurd like 2
pixels per minute.
At that point, I concluded that volumetric photon mapping was just too
absurdly slow to ever use for anything.
Ten years later, I realise what the problem was. The photon map exceeded
my computer's memory capacity, causing the puny laptop harddrive to swap
like crazy for every individual pixel.
Perhaps if I get time, I'll go see if media sampling works now, ten
years after I first tried it...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Chambers <bdc### [at] yahoocom> wrote:
> 40pps :(
This comment at the beginning of scenes/advanced/piece3/piece3.pov still
amuses me:
// Due to the large number of objects, you will probably have to
// have a lot of memory to render this scene.
// Rendering time using a 25Mhz 386 w/Cyrix fpu is approximately 60 hours.
It doesn't mention the resolution, but with a modern PC you can render
that scene in almost real-time even at a fair resolution (eg. 640x480).
Even a high resolution render (such as 1024x768) with antialiasing will
take less than 10 seconds.
(Btw, that comment in that scene file should never be removed or modified.
It's an outstanding testament of how much both PCs and POV-Ray itself have
advanced during the decades.)
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 21/06/2011 06:48 PM, Warp wrote:
> This comment at the beginning of scenes/advanced/piece3/piece3.pov still
> amuses me:
>
> // Due to the large number of objects, you will probably have to
> // have a lot of memory to render this scene.
> // Rendering time using a 25Mhz 386 w/Cyrix fpu is approximately 60 hours.
>
> It doesn't mention the resolution, but with a modern PC you can render
> that scene in almost real-time even at a fair resolution (eg. 640x480).
> Even a high resolution render (such as 1024x768) with antialiasing will
> take less than 10 seconds.
>
> (Btw, that comment in that scene file should never be removed or modified.
> It's an outstanding testament of how much both PCs and POV-Ray itself have
> advanced during the decades.)
Not just PCs. Take a look at this:
http://new.haveland.com/povbench/graphsky.php
At the bottom, we see that an Amiga powered by various flavours of
Motorola 68000 CPUs (with and without FPU) takes 8 hours to render the
same scene that a modern Intel Core 2 Duo or whatever can do in under 5
seconds.
That's a crapload of speed, right there.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Invisible <voi### [at] devnull> wrote:
> Not just PCs. Take a look at this:
> http://new.haveland.com/povbench/graphsky.php
The official benchmark results are also interesting. It's incredible how
much faster a Xeon W3580 is than a Pentium 4 (which is what I have) at the
same clockrate, even when using just one core. While the latter takes about
25 minutes to render the benchmark, the former takes only a bit over 1 minute.
That's some *serious* speedup considering that they are running at the
same clock rate.
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 22/06/2011 06:40 PM, Warp wrote:
> The official benchmark results are also interesting. It's incredible how
> much faster a Xeon W3580 is than a Pentium 4 (which is what I have) at the
> same clockrate, even when using just one core. While the latter takes about
> 25 minutes to render the benchmark, the former takes only a bit over 1 minute.
>
> That's some *serious* speedup considering that they are running at the
> same clock rate.
It puzzles me how this is possible.
Sure, the Xeon probably has a much bigger cache and a slightly faster
bus to the RAM chips. But is that *all* that makes it faster? Or is
there more to it than that? I have no idea.
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> On 22/06/2011 06:40 PM, Warp wrote:
>
>> The official benchmark results are also interesting. It's incredible how
>> much faster a Xeon W3580 is than a Pentium 4 (which is what I have) at
>> the
>> same clockrate, even when using just one core. While the latter takes
>> about
>> 25 minutes to render the benchmark, the former takes only a bit over 1
>> minute.
>>
>> That's some *serious* speedup considering that they are running at the
>> same clock rate.
>
> It puzzles me how this is possible.
>
> Sure, the Xeon probably has a much bigger cache and a slightly faster
> bus to the RAM chips. But is that *all* that makes it faster? Or is
> there more to it than that? I have no idea.
>
The Pentium 4 line is notorious ineffecient in it's use of the clock
cycles, and each of it's generations just got worst of than the previous
one. The problem was coined to an excessively long instruction pipe,
that got longer with each sub versions. It topped at over 200 steps...
It also greatly increased it's power requirments.
With the new core2, they chopped that down around 30~40 steps with the
performance boost, and power consumption decrease, we can now experiment.
A Xeon system use a more advanced I/O architecture and beter memory
management. It's instruction pipe is relatively short. It probably have
beter cache management as well as larger cache, both L1 and L2. It's L1
cache is probably distinct to the L2 cache, while the pentiums L1 cache
address space was included in the L2 address space.
Alain
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>> It puzzles me how this is possible.
>>
>> Sure, the Xeon probably has a much bigger cache and a slightly faster
>> bus to the RAM chips. But is that *all* that makes it faster? Or is
>> there more to it than that? I have no idea.
>
> The Pentium 4 line is notorious ineffecient in it's use of the clock
> cycles, and each of it's generations just got worst of than the previous
> one.
Isn't this roughly the timeframe when AMD, Cyrix and half a dozen others
suddenly popped up with compatible chips running at the same clock speed
yet delivering massively increased performance, and Intel were all like
"oh crap!"?
> The problem was coined to an excessively long instruction pipe,
> that got longer with each sub versions. It topped at over 200 steps...
> It also greatly increased it's power requirments.
>
> With the new core2, they chopped that down around 30~40 steps with the
> performance boost, and power consumption decrease, we can now experiment.
Why would you build something that's vastly harder to design yet
delivers awful performance? That doesn't make any sense. (I also don't
see how it's *possible* to have a 200-step instruction pipeline, unless
you were deliberately trying to be silly.)
> A Xeon system use a more advanced I/O architecture and beter memory
> management. It's instruction pipe is relatively short. It probably have
> beter cache management as well as larger cache, both L1 and L2. It's L1
> cache is probably distinct to the L2 cache, while the pentiums L1 cache
> address space was included in the L2 address space.
Can we really attribute all the performance advantages of 10 years of
R&D to a bigger cache and an on-board SDRAM controller?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
