Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 3 of 3 total
Thread First open of a table is slow on some machines
Thu, Mar 23 2006 5:31 PMPermanent Link

"David Zoller"
Greetings,

We have developed a plug-in for MS Outlook which opens two tables (locally)
when the plug-in is initialized. On most machines, the plug-in initializes
in under four seconds and continues. On a few machines it can take up to 13
seconds to initialize which is a very noticable slow down for users. The
difference is noticed on two identical laptops 1.7Ghz w/ 768MB.

Turning off the anti-virus on the "slow" laptop does not make a difference.

I put in some debug timing and first noticed that the slow down was on the
first VerifyTable that was issued. I took out the VerifyTables so that it
then only opened the the two TDBISAMTables. The slow down now occurs on the
first open.

These are small tables: .blb = 23KB, .dat = 8KB and .idx = 33KB

Does anyone have any suggestions?

Thanks,
DZ

Fri, Mar 24 2006 1:22 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

David,

<< I put in some debug timing and first noticed that the slow down was on
the first VerifyTable that was issued. I took out the VerifyTables so that
it then only opened the the two TDBISAMTables. The slow down now occurs on
the first open.

These are small tables: .blb = 23KB, .dat = 8KB and .idx = 33KB >>

Even with the VerifyTable calls in place, there's no way that a 8KB table
should take 13 seconds to verify/open, so there must be something external
affecting the operation.  Are you positive that the AV software is not
scanning the table(s) anymore on open ?  You can download a utility that
will show all file I/O calls here:

www.sysinternals.com

The utility is called FileMon.  It should shed some light on what is going
on.

--
Tim Young
Elevate Software
www.elevatesoft.com

Mon, Mar 27 2006 10:56 AMPermanent Link

"David Zoller"
Tim,

I have downloaded the FileMon utility and will do some experimenting when I
get a chance to get back to the timing issue. It may also be related to our
use of ExeCryptor for obfuscating the dll. I will post whatever I discover.

Thanks,
DZ

Image