[EMAIL PROTECTED] wrote:
Thanks, Dmitri
This is quite interesting. Would you mind providing a little bit more info on the
"Table Rows" part? I have three separate scenarios, one for scrolling a
1000-row table to random non-consecutive locations, one for selecting a large number of
rows and one for selecting a number of columns. My results show that Substance 5 is
currently around 30-50% slower than Nimbus, and your benchmark has Substance slower by
the factor of 2.5. I'd like to recreate such a scenario in my environment.
That benchmark adds/removes a bunch of rows, selects rows/columns in different
combinations - multiple/single/single interval selection (making them the
table scroll),
stuff like that..
Another one - D3D painting of text areas is twice slower, and D3D painting of
tables is around 30% slower (under Substance). This is interesting - what can
be a possible reason for that?
LCD text is rendered using a shader, which requires reads from the
destination surface
into a temp (also vram-based) surface. Depending on hardware this may be
slower than
rendering to a BI. However I believe on this system pure text benchmarks
are faster with the d3d pipeline, so I don't know exactly why SwngMark
benchmarks
are slower with d3d - it'd require some investigation.
Thanks,
Dmitri
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA2D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
