Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
You need to be logged in to view a user's profile.
View Replies (2)

Resolved Slow performance of SaveAsAscii in PB 2022

  1. Advice
0
Votes
Undo
  1. Jacek Karczewski
    Jacek Karczewski
  2. PowerBuilder
  3. Monday, 5 August 2024 08:36 AM UTC

Hi

We have a problem with the performance of the SaveAsAscii function (DataWindows). In PB 8, the SaveAsAscii(ls_file, "~t", "") call took 5-10 seconds, in PB 2022 R3 the same call, for the same data and the same location of the output file, takes 5-7 minutes. The output TXT file is about 13MB in size (about 30K lines) - a lot, but PB 8 handled it much better than PB 2022.

Has anyone had a similar problem? Is there a solution/workaround?

We sold our customers the upgrade from PB 8 to PB 2022 as something you must have. But with times like these... It's looks poor.

Thanks for any tips.

Best regards
Jacek Karczewski

  1. PowerBuilder (Appeon)
SQL Server SP is not executed properly through PB ...
PowerBuilder importpdf does not work for PDF docum...
Responses (2)
Jacek Karczewski
Jacek Karczewski Accepted Answer Pending Moderation
  1. Monday, 5 August 2024 12:03 PM UTC
  2. PowerBuilder
  3. # 1

Hi Chris

Thank you for quick response.

We also have a problem with SaveAsAscii in DW generated dynamically ie: dw_result.Create(ls_DWSyntax, ls_error). Here DWSyntax starts with "release 22".

Performance problems with SaveAsAscii started after we migrated our application from PB 8 to PB 12.6. I wonder if the reason is not the introduction of UTF-16 encoding in PB. Maybe conversion TXT to ANSI costs so much time...?

Regards
Jacek Karczewski

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Monday, 5 August 2024 13:13 PM UTC
Yes, this issue could have manifested itself when PB went Unicode in version 10.0. If Appeon has a test case, we can check this out in PB version 12.6 (when we got PB from SAP) to see if this is a legacy issue.
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 5 August 2024 11:30 AM UTC
  2. PowerBuilder
  3. # 2

Hi Jacek;

  Yes, that sounds very unusual. If you could create a simple test cast PB App & supply it with some external data (ie: CSV file format) to import into a DWO. Then the test case can perform the SaveAsAscii()  for that amount of time, then Appeon can take a deeper look at this performance issue. Please open a Support Ticket & attach that test case.

  Before that though, I am wondering if the issue could be your old DW objects. While the 2022 IDE will migrate all objects, it will not touch DW's. You can check this by editing the DWO source and see if the 1st line states release=22. If not, change the release number in the source & save the DWO changes. Alternatively, open the DWO in the DW Painter - change something simple (ie: tag property) - then save the DW changes. Now opening the DWO source should confirm it's migrated to 2022.

  After the above, retest the SaveAsAscii() again.  HTH

Regards ... Chris

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.