I had to let this go and get on with testing DB2 on Solaris. I had to
abandon zfs on local discs in x64 Solaris 10 5/08.
The situation was that:
* DB2 buffer pools occupied up to 90% of 32GB RAM on each host
* DB2 cached the entire database in its buffer pools
o having the file s
Richard Elling wrote:
Andrew Robb wrote:
I had to let this go and get on with testing DB2 on Solaris. I had to
abandon zfs on local discs in x64 Solaris 10 5/08.
This version does not have the modern write throttle code, which
should explain much of what you experience. The fix is available
Richard Elling wrote:
Andrew Robb wrote:
Richard Elling wrote:
Andrew Robb wrote:
I had to let this go and get on with testing DB2 on Solaris. I had
to abandon zfs on local discs in x64 Solaris 10 5/08.
This version does not have the modern write throttle code, which
should explain much of
The big problem that I have with non-directio is that buffering delays program
execution. When reading/writing files that are many times larger than RAM
without directio, it is very apparent that system response drops through the
floor- it can take several minutes for an ssh login to prompt for
