Changes between Version 167 and Version 168 of benchmarks


Ignore:
Timestamp:
Jan 29, 2013, 1:55:13 PM (13 years ago)
Author:
goddard
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • benchmarks

    v167 v168  
    197197<td> 1913 <td> 1856  <td> 207 <td> 5334 ? <td> 420
    198198<td>1509 <td>12.1 <td>10.9 <td> 36.0 <td> 21.0 <td> 60.2
    199 <td><a href="../ticket/8459">8459</a>, solid must be wrong.
     199<td><a href="../ticket/8459">8459</a>, solid must be wrong, note <a href="#note7">7</a>.
    200200<td>5/10
    201201<td>1.4.1_b30365
     
    215215<td> 1889 <td> 1750+  <td> 226 <td> ? <td> 512
    216216<td>1322 <td>603 <td>501 <td> 1895 <td> 170 <td> 142
    217 <td><a href="../ticket/11148">11727</a>
     217<td><a href="../ticket/11148">11727</a>, note <a href="#note7">7</a>.
    218218<td>1/13
    219219<td>1.7_b38101 32-bit
     
    32803280</p>
    32813281
    3282 
    32833282<a name="note6">
    32843283<p>
     
    32943293</p>
    32953294
     3295<a name="note7">
     3296<p>
     3297<b>(7)</b>
     3298The solid benchmark sometimes reports incorrect high scores, for example 10000, I believe because the texture allocation failed
     3299and Chimera is merely drawing a yellow outline box instead of drawing the data.  Something else must be going on because a
     3300size 10000 test would use a 10000 cubed volume which would not fit in memory.  Needs further investigation.
     3301</p>
    32963302}}}