If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
For 3D, would trislam be a good candidate for this? It installed fine in my two machines, but when it runs it opens a window and it doesn't draw anything in it (it always looks black), then it reports the run time, Is that the way it is supposed to be?
No, trislam wouldn't really be good for being a standard. The Perl OpenGL libraries are not too common on most Linux desktops and trislam isn't too real world representative.
Yes, that does sound about right for that test profile.
The unigine tests seem pretty interesting: realistic but also manageable download size, But they are coring in my machine, I wonder how easy it is to get them going in all the platforms of interest ... tests in this swuite should be pretty solid. Any sugestions for 3D?
The unigine tests seem pretty interesting: realistic but also manageable download size, But they are coring in my machine, I wonder how easy it is to get them going in all the platforms of interest ... tests in this swuite should be pretty solid. Any sugestions for 3D?
It seems like unigine really doesn't run in older cards. We need a more universal 3D test:
Unigine would be an excellent 3D test, especially as Unigine Corp is involved with PTS.
Sure, but what do we do about older cards? Something that could be done is just ignore the 3D test for them. Would that make sense? Can we ask Unigine Corp why they fail with a fatal error if that extension is not found? (or if there is a workaround for older cars)
Note that the score of system-quick is also the geometric mean of the other two. When you run a test, besides the global score we can show the individual scores, like in geekbench: a big number, and details beneath.
Questions:
[1] Does the composite aggregate all the individual tests od scimark2? That would be best.
[2] The regular test for build-apache builds it 3 times, way too long for this. Can we build it just once in this test?
[3] Draw circle may be limited. Can we run all "draw" tests sequentially and aggregate? (maybe not)
[4] What do we do in cases where Unigine fails? (older cards). Maybe we should only show the cpu score in that case.
Comment