FAQ's - APPX Software, Inc.: Load time, memory usage, and caching considerations when determining using GOSUB, COPY and SUBR.

APPX Knowledge Base Support answers, product how-tos, and troubleshooting guidance

	FAQ's - APPX Software, Inc. : APPX Utility : APPX Development Environment : ILF (Integrated Language Facility) : Load time, memory usage, and caching considerations when determining using GOSUB, COPY and SUBR.
	If you have a very large process like order entry. Breaking it up into separate processes and ILF subroutines can shorten initial load time since the separate process will only get loaded when it is needed for execution. This can also consume less memory and modules used less often can get cached out under the EM caching mechanism. The downside, is that there may be a very slight, theoretical, performance penalty since you are branching between separate processes, but I doubt this is a measurable difference unless you are very low on memory and other modules have to be cached back in.
	2003-Dec-31 1:12pm

Previous:	Variable Scoping considerations with GOSUB/COPY and SUBR.
Next:	Why are there lowercase I/O Verbs in ILF?

	[Search]	[Appearance]
This is a Faq-O-Matic 2.719.