Select to view content in your preferred language

Performance with API 1.1

2115
11
08-10-2011 09:22 AM
AndyKaufmann
Emerging Contributor
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?
0 Kudos
11 Replies
LanceShipman
Esri Regular Contributor
We haven't seen this issue. What environment (VS2008, VS2010, 32bit/64bit, Linux) are you using. How long of a lag are you seeing?
0 Kudos
AndyKaufmann
Emerging Contributor
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.
0 Kudos
VinceAngelo
Esri Esteemed Contributor
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
0 Kudos
LanceShipman
Esri Regular Contributor
How big is your file geodatabase? Have you seen the same behavior with the samples?
0 Kudos
AndyKaufmann
Emerging Contributor
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).
0 Kudos
LanceShipman
Esri Regular Contributor
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.
0 Kudos
AndyKaufmann
Emerging Contributor
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.
0 Kudos
LanceShipman
Esri Regular Contributor
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?
0 Kudos
AndyKaufmann
Emerging Contributor
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.
0 Kudos