Loading compiled obj code from cache to partition should not have any remarkable impact.
But you are right by principle ! It's some kind of overhead and not for free.
If you place the affected code into a .INC routine you may share that piece
rather easy over multiple instances.
Though mostly not used in that way any Include may also contain executable code.
For a :MAC routine it's nothing impressive.
For Class code it's a bit tricky but works as well
example ANNA.INC
anna(name) ;
write !,"Hello ",name,!
quit ">>>"_name_"<<<"example Anna.CLS
/// demo for Anna
Include ANNA
Class A.Anna {
ClassMethod demo(name As %String) As %String
{
quit $$anna(name)
}
}It works:
SAMPLES>write "===",##class(A.Anna).demo("robert")
===
Hello robert
>>>robert<<<
SAMPLES>So multiple loading is reduced.
You have of course also the option to compose a Custom Command in %ZLANG***.MAC
I just have no experience of how this impacts partition loading.
- Log in to post comments
.png)
.png)
.png)
.png)
.png)