Why Run-time Cost Estimation?
Static cost information in repository or catalog:
- upper bound? average?
- fluctuation in resources and load of server
- dependence on specific input data
-
Run-time cost information from megamodule:
- reflects actual load and resources
- takes into account autonomy, no out-of-date cost information in a central repository, no daily updates
- easily fits into CPAM and the concept of having several primitives for remote execution
- yet: requires in megamodule either statistics of costs over typical loads and input data gained by previous invocations, or special functionality in (wrapped) server software