topic Re: Performance with API 1.1 in File Geodatabase API Questions

Performance with API 1.1

AndyKaufmann — Wed, 10 Aug 2011 16:22:47 GMT

I just upgraded the 1.0 FGDB API code with the 1.1 code and am now seeing such a severe lag when I call CloseGeodatabase (even with a very small GDB) that I can't even test my code in debug mode. The release build (FileGDBAPI.dll) shows a lag too, though not nearly as severe. Is this something I have to live with?

Re: Performance with API 1.1

LanceShipman — Wed, 10 Aug 2011 16:32:42 GMT

We haven't seen this issue. What environment (VS2008, VS2010, 32bit/64bit, Linux) are you using. How long of a lag are you seeing?

Re: Performance with API 1.1

AndyKaufmann — Wed, 10 Aug 2011 16:40:05 GMT

We haven't seen this issue. What environment (VS2008, VS2010, 32bit/64bit, Linux) are you using. How long of a lag are you seeing?

VS2008. In debug mode when my code hits the CloseGeodatabase call it stalls for...10 minutes? I didn't feel like waiting any longer. I replicated the behavior simply with these calls:

fgdbError hr = OpenGeodatabase(filename, geodatabase);
stis_assert(hr == S_OK);
CloseGeodatabase(geodatabase);

Thanks.

Re: Performance with API 1.1

VinceAngelo — Wed, 10 Aug 2011 16:40:42 GMT

Are you testing read or write operation (or both)? Can you provide your source?

- V

[Gotta love them race conditions!]

Is this one of the sample databases? How many tables are in the dictionary?

- V

Re: Performance with API 1.1

LanceShipman — Wed, 10 Aug 2011 16:44:16 GMT

How big is your file geodatabase? Have you seen the same behavior with the samples?

Re: Performance with API 1.1

AndyKaufmann — Wed, 10 Aug 2011 16:51:59 GMT

How big is your file geodatabase? Have you seen the same behavior with the samples?

I see this behavior with the samples as well (at least Domains, Editing and Shapes--didn't try the others).

Re: Performance with API 1.1

LanceShipman — Wed, 10 Aug 2011 17:10:00 GMT

Using a fresh install of the VS2008 version of the API I don't see any slowdown in any of the samples. I'm using a Windows 7.

Re: Performance with API 1.1

AndyKaufmann — Wed, 10 Aug 2011 17:56:52 GMT

Using a fresh install of the VS2008 version of the API I don't see any slowdown in any of the samples. I'm using a Windows 7.

Hmmm. I'm using Windows 7 as well. By "install" what do you mean? I just unzipped the API archive and replaced the old files with the new ones. Is there any other way? It's not clear what could be wrong on my end since the 1.0 API code used to work fine.

Re: Performance with API 1.1

LanceShipman — Wed, 10 Aug 2011 18:00:08 GMT

I just unzipped the .zip file on a clean machine. Are you using the 32bit or 64bit version of Windows 7? Are you using a local drive or a network drive?

Re: Performance with API 1.1

AndyKaufmann — Wed, 10 Aug 2011 18:34:56 GMT

I just unzipped the .zip file on a clean machine. Are you using the 32bit or 64bit version of Windows 7? Are you using a local drive or a network drive?

64-bit Win7. Local drive for development. I'm not sure how I should "clean" my machine. I'm not quite ready to wipe the hard drive and reinstall everything. 🙂 Do the pdb files that come with the dlls mean I can stop inside CloseGeodatabase and see where it's stuck? I haven't been able to so far by telling VS the location of the symbol files. Currently when I break in the debugger it stops in thread-related code (lock) or in the function CatalogRegistry::CatalogRef::Release() under CatalogRegistry::Unregister() . That much in can see in the call stack.

Re: Performance with API 1.1

LanceShipman — Wed, 10 Aug 2011 19:22:05 GMT

64-bit Win7. Local drive for development. I'm not sure how I should "clean" my machine. I'm not quite ready to wipe the hard drive and reinstall everything. 🙂 Do the pdb files that come with the dlls mean I can stop inside CloseGeodatabase and see where it's stuck? I haven't been able to so far by telling VS the location of the symbol files. Currently when I break in the debugger it stops in thread-related code (lock) or in the function CatalogRegistry::CatalogRef::Release() under CatalogRegistry::Unregister() . That much in can see in the call stack.

A clean install in my case means a machine that does not currently have the API on it. The pdb files will not let you stop in CloseGeodatabase. I've rebuilt the samples both debug and release, 32bit and 64bit and not seen the slowdown.

Re: Performance with API 1.1

AndyKaufmann — Thu, 08 Dec 2011 18:51:29 GMT

BTW, I have the same problem with 1.1 for Visual Studio 2010. Locks up when I hit CloseGeoDatabase.
😞