Re: [Beowulf] latency and bandwidth micro benchmarks

2006-09-03 Thread Lawrence Stewart
On Aug 29, 2006, at 1:47 AM, Bill Broadley wrote: On Tue, Aug 15, 2006 at 09:02:12AM -0400, Lawrence Stewart wrote AFAIK, the canonical latency benchmark is lat_mem_rd, which is part of the lmbench suite. Really? Seems like more of a prefetch test then a latency benchmark. A fixed stride

Re: [Beowulf] latency and bandwidth micro benchmarks

2006-08-29 Thread Robert G. Brown
On Mon, 28 Aug 2006, Bill Broadley wrote: latency is much harder to get at. lat_mem_rd tries fairly hard to defeat hardware prefetch units by threading a chain of pointers through a random set of cache blocks. Other tests that don't do this get screwy results. A random set of cache blocks?

Re: [Beowulf] latency and bandwidth micro benchmarks

2006-08-28 Thread Bill Broadley
On Tue, Aug 15, 2006 at 09:02:12AM -0400, Lawrence Stewart wrote: > As has been mentioned here, the canonical bandwidth benchmark is > streams. Agreed. > AFAIK, the canonical latency benchmark is lat_mem_rd, which is part of > the lmbench suite. Really? Seems like more of a prefetch test then a

[Beowulf] latency and bandwidth micro benchmarks

2006-08-19 Thread Lawrence Stewart
As has been mentioned here, the canonical bandwidth benchmark is streams. AFAIK, the canonical latency benchmark is lat_mem_rd, which is part of the lmbench suite. Streams is ultimately a test of the bandwidth path between the drams and the core in that if you turn up the buffer size sufficie