Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Huge report scrollnextpage / Print() performance

3 posts in DataWindow Last posting was on 2009-04-19 19:26:10.0Z
Milan Stolarik Posted on 2009-04-17 18:36:32.0Z
Sender: 1640.49e8cbda.1804289383@sybase.com
From: Milan Stolarik
Newsgroups: sybase.public.powerbuilder.datawindow
Subject: Huge report scrollnextpage / Print() performance
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <49e8cc30.164a.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 17 Apr 2009 11:36:32 -0700
X-Trace: forums-1-dub 1239993392 10.22.241.41 (17 Apr 2009 11:36:32 -0700)
X-Original-Trace: 17 Apr 2009 11:36:32 -0700, 10.22.241.41
Lines: 34
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.datawindow:89178
Article PK: 418431

Hello all,
we have a serious performance issue in production with huge
datawindows (report).
When report contains many pages (4000) printing is very
slow.
This specific report has autosize high turned on on a
detail, which causes the issue.
(Other bands/groups autosize is turned off).

After retrieval, only computed field modification or zooming
takes 20 seconds.
What we noticed is, that printing using Print() method is
very slow (20 sec), than scrollnextpage right after printing
is slow (20 sec).
Another subsequent scrollnextpage is surprisingly fast.

We use printing in a loop, so we scroll down the report by
scrollnext page method finding same email address, then set
up page range and print using
Amyuni PDF converter driver.
We founds out this has nothing to do with Amyuni, printing
to normal printer in loop takes forever too.

We tried EBF 16422 " High resource usage of (GDI, User)
resources with printing and scrolling of a complex large
report".
No luck, performance was even worse.

Please help, any feedback is welcome since this is very
serious issue for our client.

Thank you very much in advance

PowerBuilder 11.2 8407


Jeremy Lakeman Posted on 2009-04-18 07:27:22.0Z
From: Jeremy Lakeman <jeremy.lakeman@gmail.com>
Newsgroups: sybase.public.powerbuilder.datawindow
Subject: Re: Huge report scrollnextpage / Print() performance
Date: Sat, 18 Apr 2009 00:27:22 -0700 (PDT)
Organization: http://groups.google.com
Lines: 47
Message-ID: <63c8aa49-191c-4916-8530-46d4cfc8b097@d19g2000prh.googlegroups.com>
References: <49e8cc30.164a.1681692777@sybase.com>
NNTP-Posting-Host: 219.90.176.174
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Trace: posting.google.com 1240039642 19592 127.0.0.1 (18 Apr 2009 07:27:22 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Sat, 18 Apr 2009 07:27:22 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: d19g2000prh.googlegroups.com; posting-host=219.90.176.174; posting-account=euaBtgoAAAC_vDxfsxmpMKlBxHaHpmRS
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.1b3) Gecko/20090305 Firefox/3.1b3,gzip(gfe),gzip(gfe)
Path: forums-1-dub!forums-master!newssvr.sybase.com!news-sj-1.sprintlink.net!news-peer1.sprintlink.net!newsfeed.yul.equant.net!nntp1.roc.gblx.net!nntp.gblx.net!nntp.gblx.net!nlpi057.nbdc.sbc.com!prodigy.net!border1.nntp.dca.giganews.com!nntp.giganews.com!postnews.google.com!d19g2000prh.googlegroups.com!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.datawindow:89179
Article PK: 418434


On Apr 18, 3:36 am, Milan Stolarik wrote:
>  Hello all,
> we have a serious performance issue in production with huge
> datawindows (report).
> When report contains many pages (4000) printing is very
> slow.
> This specific report has autosize high turned on on a
> detail, which causes the issue.
> (Other bands/groups autosize is turned off).
>
> After retrieval, only computed field modification or zooming
> takes 20 seconds.
> What we noticed is, that printing using Print() method is
> very slow (20 sec), than scrollnextpage right after printing
> is slow (20 sec).
> Another subsequent scrollnextpage is surprisingly fast.
>
> We use printing in a loop, so we scroll down the report by
> scrollnext page method finding same email address, then set
> up page range and print using
> Amyuni PDF converter driver.
> We founds out this has nothing to do with Amyuni, printing
> to normal printer in loop takes forever too.
>
> We tried EBF 16422 " High resource usage of (GDI, User)
> resources with printing and scrolling of a complex large
> report".
> No luck, performance was even worse.
>
> Please help, any feedback is welcome since this is very
> serious issue for our client.
>
> Thank you very much in advance
>
> PowerBuilder 11.2 8407

Have you tried filtering by email address, so there aren't that many
rows in the primary buffer?
Also you might want to cut down on the computed fields, especially if
they call functions. As they will be evaluated whenever PB needs to
display them or calculate their size.

One idea I've used before is to have a number of extra column objects,
with the computed expression they use in their tag property.
Then after retrieving you describe('evaluate("<expression>",<row>)')
and put the value in the column. Then you know you are only evaluating
each expression once.