• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • Application Slowness when printers are working slow

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (2)

Resolved Application Slowness when printers are working slow

  1. Advice
0
Votes
Undo
  1. Balu Krishnasamy
    Balu Krishnasamy
  2. PowerBuilder
  3. Monday, 12 November 2018 20:06 PM UTC

Hello - I've been hearing this strange issue from my support that the application is slowing down drastically when it tries to open up certain windows especially when the printers work slowly (it'd pause anywhere from 10s to 2m) trying to reach the printer.

I couldn't possibly seem to envision a relationship between the printers and the slowness caused while opening a window. The windows has some tabs /tab pages, dw container and dwo to the container. No print method is called but few retrievals on open. I am not sure how the printers are related here. Could some one please advise if they had encountered similar issues.

Also, the same behavior is related to splwow64.exe, an instance of splwow64 fires up on the application open and stays open even if the application is closed. 

Its a PB 12 application with SQL Anywhere mostly running on Win10.

Thanks for your thoughts/help!

~Balu

where I can download "PostgreSQL Native Drive" (fo...
PDFs are being saved with wrong data
Responses (2)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 12 November 2018 20:21 PM UTC
  2. PowerBuilder
  3. # 1

Hi Balu;

   FYI: DataWindow objects draw their fonts from the current printer. If the current printer is remote, or the printer does not have the DWO fonts requested, the DWO will synthesize these "on-the-fly" - however, this can indeed be very slow to derive for each DWO used in a Window class.

   Make sure first of all that your PB Apps are using TrueType fonts that are provided in the W10 O/S default installation. Then try (if possible) to set the default printer to a local one (ie: using the SetPrinter() command).

   Note: Running under Cirtix can make the DWO font situation worse as well.

FWIW: I use the MS-Office standard for all my PB apps (Tahoma 8 point).

HTH

Regards ... Chris

Comment
Balu Krishnasamy
  1. Balu Krishnasamy
  2. Monday, 12 November 2018 20:37 PM UTC
Chris, Much Appreciated as always!

Our standard font is MS Sans Serif (so no issues there i guess) and this issue is mostly on a Terminal Server environment (which explains from your answer). This totally makes sense.

Thanks again for your time!
  1. Helpful
There are no comments made yet.
Balu Krishnasamy
Balu Krishnasamy Accepted Answer Pending Moderation
  1. Tuesday, 13 November 2018 14:27 PM UTC
  2. PowerBuilder
  3. # 2

Also, do we know if the usage of splwow64.exe got any better with PB2017 R3? Thanks!

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.