× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



> From: Vern Hamberg
> 
> Joe, it's not really caching, it's just the result of data being in
memory
> that is available to all processes. Unit testing would need you to
CLRPOOL
> and SETOBJACC *PURGE in order to compare apples to apples. Another
kind of
> testing would be what you are doing now, to show what happens when you
> leave things in memory.

Um, why would I need to CLRPOOL to compare "apples to apples"?  Are you
saying that somehow CLRPOOL will make SQL run better?  Why?  Does SQL
not know how to take advantage of memory?  If so, that's a knock on SQL,
not my testing.  Since I would never be doing a CLRPOOL in production,
why would I do it in a test?

Just trying to find out what you consider "apples to apples" to really
mean.

Joe


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.