Kevin Cully wrote:
I've just started a new task with a client to speed up their
application startup time. Specifically for the users that are running
the application over the network. They are using a Visual Maxframe
Professional framework. I've brought the application local to my
network and I'm pouring over the coverage profiler.
The thing that is really killing performance is a SET PROCEDURE call.
It is taking over 18 seconds!!!
* There are 13 PRGs in the SET PROCEDURE command
* This is a situation where they're saving the state of the SET
PROCEDURE, doing some code and then restoring the SET PROCEDURE state.
* Strangely, some of the references have the full path to the FXP,
others don't even though they're set in the same manner.
* These PRGs are "excluded" from the project, so aren't compiled into
the EXE.
* For the VMP experts out there, this is called in the Destroy of the
cusPushPopSetTo class.
Any performance tips?
Hmmm....what's the SET PATH? I wonder if it's searching in the PATH and
that's spread way out (not local) somewhere? Just a wag...
--Michael
--
Michael J. Babcock, MCP
MB Software Solutions, LLC
http://mbsoftwaresolutions.com
http://fabmate.com
"Work smarter, not harder, with MBSS custom software solutions!"
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
