somebodyspecial writes:
> I didn't realize mem would be such an issue, but I'd certainly like
> to see some AMD vs. NV (opencl vs. cuda) to prove that in adobe.
Adobe what? ;D From what I've read, the various Adobe apps behave
quite differently for these things.
> saying I didn't realize it to be an overall problem in all things
> adobe (thought that to be more of a niche comment but maybe not).
It might not be, I don't know. I'm not familiar with how Photoshop
& Premiere handle data & RAM allocation. I only know it's very
important for AE.
> But your comment brings up an interesting test I'd like to see, and
> maybe the difference between 8/32gb, ...
Toms' tests have already said many times in the past that AE tests
done with 8GB systems should be taken with a pinch of salt since
they're not realistic, being RAM limited.
> I'd take even that scenario...LOL). At least we'd have some
> relevant CUDA vs. OpenCL data we could make purchase decisions on. I
I was going to say I'd try this, but I don't have a modern AMD
card yet. Still hunting. I do plan on testing AE on a couple of
older configs with 16GB, see how it behaves, but not yet, other
things to sort first.
> the same thing to get the point across but I digress...
😉 Sorry
> people like you have to keep seeing it..
🙁
I understand your implied point, but alas in the real world it's
more difficult to demonstrate some of the things you're asking
about. Even with the same application, two different datasets
might behave quite differently. Simply using or not using an old
effect like Shatter can completely alter the amount of RAM the
app grabs, how many threads are involved, the GPU loading, etc.,
which means the bottlenecks can change from one part of a render
to another, or indeed during the same frame.
> data in a few areas of toms tests
But I don't care to see ANY
> OpenCL test run on NV hardware if there is a CUDA option. Opencl
I understand why, but it would mean someone with an existing AMD
setup, combining both types of test, can compare what happens for
upgrading to a newer AMD vs. switching to NVIDIA.
> one is pitted against the other. Sighting one sides scores is
I agree, though sadly I do get the impression that Adobe itself is
leaning deliberately towards AND GPUs. Maybe it's a cost issue.
> You may be right in what Chris would say for his reasons (but why
> do they avoid responding to questions about this?). But I'd ask why
Avoid? Could be they're just busy. They have a huge workload.
😀
>in real world use? I mean like testing cpus in 640x480 when it will
Usually such measures are taken in order to isolate the testing in
a particular way, to focus the workload on the CPU, otherwise it
becomes a system test rather than a CPU test, but i know what you mean.
> Either way, I enjoy your posts and hope Tom's read them and starts
> giving us more complete data (probably a better way to put that but
A friend of mine is sorting out an AE CUDA test they could use, but
whether or not they can do the kind of tests you've been describing,
that I don't know. Limited time, resources, etc. Hard to say.
> ... I get more from some
> of your comments than the parts of toms articles that pertain to
> this topic. ...
Careful, if my head gets any bigger it'll need its own post code.
😀
> with few configs available to me now). ...
I have a fairly wide range now, more than a dozen mbds/systems
with over a hundred different possible CPU/GPU combinations. I've
certainly come to appreciate toms author comments about the practical
issues involved in doing such tests. It's hellishly time consuming.
> building pro-e/solidworks/cad/FAE etc stations for engineers and had
That's sort of what I've started doing, though ironically I don't
have any of those apps to use for real-world tests, only benchmarks
like Viewperf, so I can't test some of the things I mentioned
earlier such as big data sets that might stretch main RAM or GPU RAM.
> for a time worked with DEC Alphas also with FX!32 or not depending
Ahh DEC Alphas... how I once used to long after a 21264 just for
fiddling.
😀 But that was before I bagged a 32-CPU SGI...
😉
> Happy New Year
Ditto. 8)
Ian.