The right thing to do is build two versions of the code, with existing and T2000 optimizations, then run both versions on existing and T2000 systems. You get four sets of results and can separate the hardware from the software effects.
Could you post a link to the results when you get them? Adrian On 10/31/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
There isn't any one answer to this question. Do you intend to use this T2000 specific compilation option when you compile the applications that you actually intend to run on this platform? What does the option do? Usually it is desireable to use architecture specific optimizations in benchmarks when you're using the results for competitive analysis, ie. benchmarks for marketing purposes. However, if you're actually trying to analyze the results of the benchmark for engineering purposes, it makes more sense to eliminate variation and use a consistent set of options across all platforms. I hope this helps. -j On Mon, Oct 30, 2006 at 08:35:43AM -0800, JPL wrote: > I ran LibMicro tools on a T2000 and I'm wondering if I should use T2000 specificl compilation option or not . > > I intend to use the tools to compare T2000 versus V890 > > JP > > > This message posted from opensolaris.org > _______________________________________________ > perf-discuss mailing list > perf-discuss@opensolaris.org _______________________________________________ perf-discuss mailing list perf-discuss@opensolaris.org
_______________________________________________ perf-discuss mailing list perf-discuss@opensolaris.org
