try valgrind too if you haven't.
On 10/3/05, Miguel A Paraz <[EMAIL PROTECTED]> wrote: > On 9/30/05, Orlando Andico <[EMAIL PROTECTED]> wrote: > > try using "lmbench" > > it will show a nice graph showing your memory latency. you'll see a big jump > > at the L1 cache size, and another big jump at the L2 cache size. > > > > my ancient article on linux benchmarking (as in 4-year old article) delved > > into this quite a bit. > > Thanks. Nasty tool. I haven't read the source but I wonder how you can > check cache performance from C code. > > I'm curious how my system does under real workloads, though. I suspect > my 256 KB L2 is sufficient since I'm not doing "real time" work, like > games - the main reason people get full Pentiums and Athlon 64s! > _________________________________________________ > Philippine Linux Users' Group (PLUG) Mailing List > [email protected] (#PLUG @ irc.free.net.ph) > Read the Guidelines: http://linux.org.ph/lists > Searchable Archives: http://archives.free.net.ph > _________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List [email protected] (#PLUG @ irc.free.net.ph) Read the Guidelines: http://linux.org.ph/lists Searchable Archives: http://archives.free.net.ph
