> Can anyone speak factually about internal cache in Unidata? I would be looking more at the operating system than UniData when it comes to results like this. With the amount of memory available on today's systems, it's likely that major portions (if not all) of the file(s) are remaining in O/S cache. So for second and subsequent queries you're pulling from memory instead of disk. If you really want to get a fair estimation of one query method versus another, you really should reboot between each invocation. OK - that's generally not practical, so you probably want to perform each query twice, ignoring the first one each time. That won't give you an indication of how things will perform in real life, but it will give you some sort of idea of how one method compares to another.
It's interesting to note that your second of three queries changes drastically during the second invocation while the others remain the same. Without knowing anything about your files or the dictionary items involved, I'm going to guess that XCDD.DIV involves one or more file translates. The records in the file(s) being referenced are being cached during the first invocation and available in memory the second time around. Tim Snyder Consulting I/T Specialist U2 Lab Services Information Management, IBM Software Group ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
