My approach was rather simple.
- in runtime any class has its .INT wich has its .OBJ
- the OBJ is in the partition.
- if I stay inside the .OBJ it's fine
- if I have to load another .OBJ and then reload the original .OBJ it consumes processor cycles
- both .OBJ can be assumed to be cached, so it's a pure memory exercise
- the difference of both variants is sub microscopic
- so looping for 100 M is kind of zoom-in to get something visible
- The 100 M are common to both scenarios and
- the Global has only (800 Mb) >>> 8 bytes / record counted by
- I decided for SQL Shell for its nice runtime display.
SUMMARY: There is a difference.
But I wouldn't bend a little finger to attack it. (not even on PDP-11)
This is nothing where performance comes from.
- Log in to post comments
.png)
.png)
.png)
.png)
.png)