...

>
> If you have the time and a suitable database I'd be happy to share what I was
> doing with you. Suitable, in this case, is a database with two tables each large
> enough to be bigger than the largest possible cache. This allows us to a) See
> how long it takes to fill the cache and b) see the benefit of a full cache on
> repeating the select. The second large table is used to flush the first table
> from the cache.
>
> Paul
> --

If this can be done at my workplace, I have a database with about 30
tables, total size 2.5-3GB. One of the tables has 6.000.000+ records
(uncompressed records size approx 200B), another table has 2.000.000+
records (haven't counted bytes, but will probably fit the specs). It is
running on IB/5.6 (2x200MHz PPro, WinNT4SP6 - soon to be moved to
2x800MHz Zeon and fast disks, Win2k). If your test setup can be run
without to much disrupting of daily database use, I'd like to know more.
Another possibility is an 800MB database I have at home, running on
550MHz PIII.

Regards,
Aage J.