[Progress Communities] [Progress OpenEdge ABL] Forum Post: PASOE Performance Issue with NEWING class

  • Thread starter Thread starter Roger Blanchard
  • Start date Start date
Status
Not open for further replies.
R

Roger Blanchard

Guest
We just ran into an issue with a customer that just migrated from 11.4 Classic Appserver to 11.7.5 PASOE. The system was just running slow...... We narrowed it down to backend logic. We then narrowed it down to our logging mechanism. We then narrowed it down to NEW ClassName (). It appears that NEWING a class in PASOE is 22x slower than doing the same in a GUI client (WebClient) I just threw together a quick repro. The WriteMessage METHOD has no code in it so nothing is being done. On GUI Client; The following takes 1312ms when just passing a CHAR DO iCnt = 1 TO 1000000: LogManager:WriteMessage("Test1", "ORS_APP" // we only want this to be logged if ORS_APP is enabled which is old logging ). END. The following takes 5268ms so about 4x slower DO iCnt = 1 TO 1000000 ON ERROR UNDO, THROW: LogManager:WriteMessage("Test1", NEW MessageSubSystem ("ORS_APP") // we only want this to be logged if ORS_APP is enabled which is old logging ). END. On PASOE server; The following takes 1531ms when just passing a CHAR. DO iCnt = 1 TO 1000000: LogManager:WriteMessage("Test1", "ORS_APP" // we only want this to be logged if ORS_APP is enabled which is old logging ). END. The following takes 120324ms so 22x slower than the same code on the GUI client. DO iCnt = 1 TO 1000000 ON ERROR UNDO, THROW: LogManager:WriteMessage("Test1", NEW MessageSubSystem ("ORS_APP") // we only want this to be logged if ORS_APP is enabled which is old logging ). END. Is this expected? I would hope not.

Continue reading...
 
Status
Not open for further replies.
Back
Top