[progress Communities] [progress Openedge Abl] Forum Post: Re: Query Performance - How Can...

[ChUIMonster]

That is the proper article. It goes into quite a lot of detail on how these things work. I have found _actServer to be reliable. But you might need to make arrangements to isolate your test cases. Or maybe use a reliable OS? Anyhow... I test with a copy of sports that I am the only user of. That makes my traffic much easier to identify and analyze. My test harness looks like this: /* foreach.p */ {actsrv_hdr.i} {actsrv_init.i} for each _field no-lock: /* test 1 */ end. {actsrv_end.i "for each"} {actsrv_init.i} for each _field fields( _field-name ) no-lock: /* test 2 */ end. {actsrv_end.i "for each fields()"} The include files: /* actsrv_hdr.i */ define variable msgRecv as integer no-undo. define variable msgSent as integer no-undo. define variable recSent as integer no-undo. define variable qryRecv as integer no-undo. /* actsrv_init.i */ find _actServer no-lock where _Server-id = 2. assign msgRecv = _Server-msgRec msgSent = _Server-msgSent recSent = _Server-recSent qryRecv = _Server-QryRec . etime( yes ). /* actsrv_end.i */ find _actServer no-lock where _Server-id = 2. assign msgRecv = _Server-msgRec - msgRecv msgSent = _Server-msgSent - msgSent recSent = _Server-recSent - recSent qryRecv = _Server-QryRec - qryRecv . output to value( "nettraffic.txt" ) append. put ( msgRecv + msgSent ) format ">>>,>>>,>>9" qryRecv format ">>>,>>>,>>9" recSent format ">>>,>>>,>>9" ( recSent / qryRecv ) format ">>>,>>>,>>9" etime format ">>,>>9" . put unformatted " " trim( sessionarameter + " {1}" ) skip. output close.

Continue reading...