Just noticed that when
set coverage to logfile.log
was active, the load time was different.
On the FAST configuration, it took 6 seconds instead of 1/2.
On the SLOW config, it took only took 16 seconds instead of 78!
I can understand how all the overhead from the logging could slow the
FAST config down, but causing the SLOW configuration to speed up by a
factor of 4 is, again, bizarre. It really does, in my opinion, keep
pointing at the OCX file dragging its feet. It might just be me but it
seems that by VFP getting "in the loop" and writing to the coverage log,
it forced the OCX routine to release or timeout or something.
Interesting...and unfortunately the "black box" mentality that the OCX
option provides is now both a benefit and a hinderance. Something is
going on "in there" and I have no way of doing anything about it. (Makes
Open Source look more and more attractive...)
Mike
> Mike Copeland wrote on 2011-03-03:
>> Tracy,
>>
>> I may be misunderstanding your focus, but the AddComboItem loop is in
>> the Init of the form, before the form ever displays. Once the form
>> displays, there are no speed issues and the combo is never loaded
>> again....until a new instance of the form is called for.
>>
>> The code in each of the ctGrid methods and events have to do with
>> recalculating tax (calling a form method) popping up a messagebox if
>> they enter an unknown "off the list" SKU, etc. None of them cause the
>> ctGrid to redraw, adjust, or be modified in any way, either on purpose
>> or not-on purpose.
>>
>> I turned off Windows Themes in the Win7 Control Panel>Personalization,
>> no change.
>>
>> Set sys(2700,1) in the beginning of my MAIN.PRG, and it actually
>> increased the times, on both the FAST and the SLOW scenarios.
>>
>> Bizarre!
>>
>> Mike
>>
> Mike,
>
> No, I think you understood where I was heading. It isn't making sense. There
> was an odd behavior seen once in my application that I've not been able to
> take the time to track down. It is related to VFP 9 SP 2 runtimes on my
> compiled with VFP 9 SP 1. I've not been able to make the time to track it
> down since most clients are not running that configuration. It has something
> to do with a loop process and updating records in tables. No ActiveX
> controls involved, so the scenario is only similar by the SP 2. As I'm
> typing, I recall it was happening on XP workstations too. I don't have any
> more direction.
>
> Since VFP 9, you can capture the coverage profile logging on with SET
> COVERAGE TO... in the runtime.
>
> Tracy Pearson
> PowerChurch Software
>
>
>
>
[excessive quoting removed by server]
_______________________________________________
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
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.
