[6.1] RB/Progress Issue

Yahoo Archive
1
We recently upgraded our Vantage server to a whole new setup, but the
biggest performance increaser by-far was the amount of RAM the server
had. I believe this was the soure of all of our long-running report
woes. Reports that took hours now takes minutes or seconds! All this
due to a jump from 2 Gigs of RAM to 8Gigs of RAM. Considering that it
takes nanoseconds to address memory, as compared to microseconds to
address virtual memory, I bet you would find that your server is running
from virtual memory on those longer running reports.



Andrew Reed
Crestview Aerospace Corp.


________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Todd Caughey
Sent: Thursday, June 29, 2006 11:40 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] [6.1] RB/Progress Issue



Thanks. I knew Memo was an issue from other reports. I already linked
the Related-to-table = "Customer' and the CategoryCode = 'CRD' but as
you say Key1 = CustNum does not work due to the type difference. But the
filter on this (Key1 - CustNum or Key1 = ?), after all other relevant
filters have been satisfied, should not result in the tha much of a hit.
Other reports using Memos for Customers run in seconds.

I have tweaked a few more things and am running it again now at lunch
time when fewer people will complian. More so than the speed is the
interference issue and I was thinking they might be related...as in a
"deadly embrace" locking situation. Running a RB report should never
kill the rest of Vantage like this.

-Todd C.


-----Original Message-----
From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ]On
Behalf Of Keith Mailloux
Sent: Thursday, June 29, 2006 10:24 AM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: RE: [Vantage] [6.1] RB/Progress Issue

Todd,

I suspect it is the use of the memo table. We have a few reports we use
that access the memo table. We had to write a little utility program to
populate vb fields to create the proper index keys to link with the memo
table. If you will notice the "key" fields are character while quite
often your field in the related table is numeric such as quote number or
invoice number and the "RelatedtoFile" is also part of the available
index scheme. You need to be able to include these in your links
otherwise you get sequential reads to the memo table contents which can
kill performance.

One thing I do when this occurs is remove links one at a time or if
building from scratch add them one at a time and check performance. You
can usually find the culprit that way. Since you don't have the problem
on all reports I would start there. If you want more info on the joining
to the memo table give me a call.

Keith Mailloux

Ferguson Perforating

(401)941-8876

________________________________

From: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
[mailto: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com] On
Behalf
Of Todd Caughey
Sent: Thursday, June 29, 2006 11:01 AM
To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
Subject: [Vantage] [6.1] RB/Progress Issue

I have what is probably a Progress related issue with Report Builder.
Lately (within the last couple patch releases - now on 536) I have seen
two things happen with certain RB reports...
1) they run SLOOOOOOW and
2) they cause ALL of Vantage for everyone to grind to a virtual halt.

I know how to optimize RB reports (linking and filters) and these are
reports that should take only a few minutes to run but now can take
several hours. The part worrying me the most is impact on everyone else.
I have double checked the database connection on the reports and the
"Multiple Users" box is checked (if that matters).

For example I have an A/R aging report with the following tables:
InvcDtl
InvcHead
CashDtl
Customer
Terms
CustCnt
Memo

I know the memo part can be a performance hit due to filtering but
nothing to the extent I am seeing. But just why doing anything with
those tables freezes shop data collection or prevents creating packing
slips totally escapes me. When the shop supervisors call me and I end
the task everyone instantly take off like normal.

Any ideas why RB is impacting the whole system and/or suggestions for
Progress settings to accomodate RB?

Thanks,
Todd Caughey
Harvey Vogel Mfg. Co.

[Non-text portions of this message have been removed]

---------------------------------
This e-mail and any attachments may contain confidential and
privileged information. If you are not the intended recipient,
please notify the sender immediately by return e-mail, delete this
e-mail and destroy any copies. Any dissemination or use of this
information by a person other than the intended recipient is
unauthorized and may be illegal.

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]






[Non-text portions of this message have been removed]
2
I have what is probably a Progress related issue with Report Builder. Lately (within the last couple patch releases - now on 536) I have seen two things happen with certain RB reports...
1) they run SLOOOOOOW and
2) they cause ALL of Vantage for everyone to grind to a virtual halt.

I know how to optimize RB reports (linking and filters) and these are reports that should take only a few minutes to run but now can take several hours. The part worrying me the most is impact on everyone else. I have double checked the database connection on the reports and the "Multiple Users" box is checked (if that matters).

For example I have an A/R aging report with the following tables:
InvcDtl
InvcHead
CashDtl
Customer
Terms
CustCnt
Memo

I know the memo part can be a performance hit due to filtering but nothing to the extent I am seeing. But just why doing anything with those tables freezes shop data collection or prevents creating packing slips totally escapes me. When the shop supervisors call me and I end the task everyone instantly take off like normal.

Any ideas why RB is impacting the whole system and/or suggestions for Progress settings to accomodate RB?

Thanks,
Todd Caughey
Harvey Vogel Mfg. Co.


[Non-text portions of this message have been removed]
3
Todd,



I suspect it is the use of the memo table. We have a few reports we use
that access the memo table. We had to write a little utility program to
populate vb fields to create the proper index keys to link with the memo
table. If you will notice the "key" fields are character while quite
often your field in the related table is numeric such as quote number or
invoice number and the "RelatedtoFile" is also part of the available
index scheme. You need to be able to include these in your links
otherwise you get sequential reads to the memo table contents which can
kill performance.



One thing I do when this occurs is remove links one at a time or if
building from scratch add them one at a time and check performance. You
can usually find the culprit that way. Since you don't have the problem
on all reports I would start there. If you want more info on the joining
to the memo table give me a call.



Keith Mailloux

Ferguson Perforating

(401)941-8876





________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Todd Caughey
Sent: Thursday, June 29, 2006 11:01 AM
To: vantage@yahoogroups.com
Subject: [Vantage] [6.1] RB/Progress Issue



I have what is probably a Progress related issue with Report Builder.
Lately (within the last couple patch releases - now on 536) I have seen
two things happen with certain RB reports...
1) they run SLOOOOOOW and
2) they cause ALL of Vantage for everyone to grind to a virtual halt.

I know how to optimize RB reports (linking and filters) and these are
reports that should take only a few minutes to run but now can take
several hours. The part worrying me the most is impact on everyone else.
I have double checked the database connection on the reports and the
"Multiple Users" box is checked (if that matters).

For example I have an A/R aging report with the following tables:
InvcDtl
InvcHead
CashDtl
Customer
Terms
CustCnt
Memo

I know the memo part can be a performance hit due to filtering but
nothing to the extent I am seeing. But just why doing anything with
those tables freezes shop data collection or prevents creating packing
slips totally escapes me. When the shop supervisors call me and I end
the task everyone instantly take off like normal.

Any ideas why RB is impacting the whole system and/or suggestions for
Progress settings to accomodate RB?

Thanks,
Todd Caughey
Harvey Vogel Mfg. Co.

[Non-text portions of this message have been removed]





---------------------------------
This e-mail and any attachments may contain confidential and
privileged information. If you are not the intended recipient,
please notify the sender immediately by return e-mail, delete this
e-mail and destroy any copies. Any dissemination or use of this
information by a person other than the intended recipient is
unauthorized and may be illegal.

[Non-text portions of this message have been removed]
4
Thanks. I knew Memo was an issue from other reports. I already linked the Related-to-table = "Customer' and the CategoryCode = 'CRD' but as you say Key1 = CustNum does not work due to the type difference. But the filter on this (Key1 - CustNum or Key1 = ?), after all other relevant filters have been satisfied, should not result in the tha much of a hit. Other reports using Memos for Customers run in seconds.

I have tweaked a few more things and am running it again now at lunch time when fewer people will complian. More so than the speed is the interference issue and I was thinking they might be related...as in a "deadly embrace" locking situation. Running a RB report should never kill the rest of Vantage like this.

-Todd C.


-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]On Behalf Of Keith Mailloux
Sent: Thursday, June 29, 2006 10:24 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] [6.1] RB/Progress Issue



Todd,

I suspect it is the use of the memo table. We have a few reports we use
that access the memo table. We had to write a little utility program to
populate vb fields to create the proper index keys to link with the memo
table. If you will notice the "key" fields are character while quite
often your field in the related table is numeric such as quote number or
invoice number and the "RelatedtoFile" is also part of the available
index scheme. You need to be able to include these in your links
otherwise you get sequential reads to the memo table contents which can
kill performance.

One thing I do when this occurs is remove links one at a time or if
building from scratch add them one at a time and check performance. You
can usually find the culprit that way. Since you don't have the problem
on all reports I would start there. If you want more info on the joining
to the memo table give me a call.

Keith Mailloux

Ferguson Perforating

(401)941-8876

________________________________

From: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com [mailto: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com] On Behalf
Of Todd Caughey
Sent: Thursday, June 29, 2006 11:01 AM
To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
Subject: [Vantage] [6.1] RB/Progress Issue

I have what is probably a Progress related issue with Report Builder.
Lately (within the last couple patch releases - now on 536) I have seen
two things happen with certain RB reports...
1) they run SLOOOOOOW and
2) they cause ALL of Vantage for everyone to grind to a virtual halt.

I know how to optimize RB reports (linking and filters) and these are
reports that should take only a few minutes to run but now can take
several hours. The part worrying me the most is impact on everyone else.
I have double checked the database connection on the reports and the
"Multiple Users" box is checked (if that matters).

For example I have an A/R aging report with the following tables:
InvcDtl
InvcHead
CashDtl
Customer
Terms
CustCnt
Memo

I know the memo part can be a performance hit due to filtering but
nothing to the extent I am seeing. But just why doing anything with
those tables freezes shop data collection or prevents creating packing
slips totally escapes me. When the shop supervisors call me and I end
the task everyone instantly take off like normal.

Any ideas why RB is impacting the whole system and/or suggestions for
Progress settings to accomodate RB?

Thanks,
Todd Caughey
Harvey Vogel Mfg. Co.

[Non-text portions of this message have been removed]

---------------------------------
This e-mail and any attachments may contain confidential and
privileged information. If you are not the intended recipient,
please notify the sender immediately by return e-mail, delete this
e-mail and destroy any copies. Any dissemination or use of this
information by a person other than the intended recipient is
unauthorized and may be illegal.

[Non-text portions of this message have been removed]







[Non-text portions of this message have been removed]