This did end up being custom code. Since it was written to the cconsole.log, my assumption was that it was native.

Currently, we are running 2010.2 and I am following this to review our performance. In doing so, I read above, "The maximum size of routine buffers is 1023 MBs."

I was wondering if you could clarify what this means as I'm finding that the maximum is 65,535.

Thanks in advance.

The following is the capture requested with the exception of the fields that were trimmed due to them all being 0. The fields trimmed were RemGrefs, GRratio, RemGupds, RemRrefs, RemRLaS, GblSz, pGblAsz, RouSz, pRouAsz, ObjSz, pObjAsz, ActECP, Addblk, PrgBufL, PrgSrvR, BytSnt, BytRcd, and IJULock.

mgstat-capture

This does work for intermediate routines; however, it didn't seem to work with MAC routines. Do you know of a method for making changes to the MAC routines?

Thanks for the response; however, I am trying to determine our rate of consumption, which we would need to know the formula for the consumption of storage and not for what has already been consumed.

This does not identify how consumption may be calculated; however, it does advise how we can determine how much storage a global has already consumed. I am looking for how to calculate consumption, which would help us in identifying our personal rate of consumption.

EDIT: It may be worth noting that when reviewing a global with this class the output was 0.008 for multiple tests, where ^%GSIZE provided varying bytes for each test.

Due to receiving the Zen .js errors, I was unable to use the Global Mappings page; however, I was able to change the Default Database for Globals to BetaDB and then use the following to provide the solution.

%SYS>s Properties("Database")="AlphaDB", Status=##Class(Config.MapGlobals).Create("Alpha","Customers(BEGIN):(10000001)",.Properties)

Yes. However, I'm not showing where in the documentation, or in the link you've provided, it showing what I've asked. I'm not sure how efficient it would be to place 10M references in the global mappings. Are you seeing something in the referenced link that addresses the issue discussed?