I have used the coverage log in the past to pin point the exact line or lines of code that is causing the slow down.
Set coverage to test.log -----Original Message----- From: ProFox [mailto:[email protected]] On Behalf Of Peter Cushing Sent: Tuesday, August 26, 2014 7:39 AM To: [email protected] Subject: Re: Cause of slowdown on one machine, VFP7, after a few hours Ted Roche wrote: > <snip> > User reports slowdown > after 2 hours of intensive work, Sounds like they are working too hard. Do they have a union ;-) > not reproducible here, and not solved by turning on/off application or > rebooting workstation. > > Rather than spend days attempting to repro problem. the lead developer > on this project wants to roll back exe and data structures to > previously-known stable config (back around May) and confirm problem > is gone, then roll foreward. Not being involved day-to-day in the dev > nor ops for this app, I'm inclined to run with that plan and see if it sheds light on the issues. > > If that produces nothing an idea might be to get the code to write out to a log file at critical points to hopefully show you where the bottleneck is. Peter [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** 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.
