D
dbeavon
Guest
Yes, we run code off of a NAS (NetApp). I've watched the file IO from Progress when it is running a program for the first time and it seems very resource-intensive, mainly because of the various entries in the PROPATH. Thankfully the "-q" parameter prevents the NAS from being abused too badly when the same r-code is executed over and over in a loop. Shelly, I like your idea of gathering the r-code and deploying to a single destination. I think we'd have to do the same for all our source code files because we still do a lot of dynamic compilation via query/results. That dynamic compilation requires much of our source code to be deployed alongside the compiled code. It would be nice if some PROPATH precedence hints could be incorporated into the compiled r-code for a program or class . The hints might suggest the order to use when searching the paths at runtime for a given class. IE. At compile-time the ABL compiler must resolve the references to other OO classes, and that information could be preserved for use by the runtime. If the compiler found the related classes in a given PROPATH directory or pl file, then the information doesn't need to be forgotten. It could be used by the AVM to look for the class in the most likely place, before eventually searching the entire PROPATH sequentially.
Continue reading...
Continue reading...