span8
span4
span8
span4
How can I improve the performance when working with Esri Geodatabases?
Note: Esri ArcSDE has beendeprecatedso this is no longer an option in newer versions of Esri products and FME
The Esri ArcSDE reader/writer generally provides better performance than the Esri Geodatabase (ArcSDE) reader/writer.This is because the Esri ArcSDE writer allows buffered writes, which can improve the performance of loading data you know will load cleanly.If you are concerned about performance, use the Esri ArcSDE writer if possible.You may need to create the feature classes with the Esri Geodatabase (ArcSDE) writer, then insert into them with the Esri ArcSDE writer.
The Esri ArcSDE reader/writer writes directly to the SDE feature classes avoiding the ArcGIS API used by the Esri Geodatabase (ArcSDE) reader/writer.You can only reader or write simple features with the Esri ArcSDE.
Try using the Esri Geodatabase (File Geodatabase Open API) reader/writer if you're only reading or writing simple features to a file Geodatabase.It avoids the overhead of the ArcGIS Geodb API.
You might also try using FME 64bit instead of FME 32bit.Overall, FME 64bit versions should give you improved performance.You can use FME 64bit versions to read or write to Geodatabases if you install the ArcGIS 64bit Geoprocessing Engine, refer to:Esri Formats Supported by my FME Version
You can speed up translations involving all writers bylengthening the interval between committing transactions.Committing transactions is an expensive operation, and therefore it is recommended that you make the transaction interval as big as possible.In speed tests performed at Safe Software, changing the transaction interval from 500 to 1000 resulted in a specific translation being 2.5% faster.Changing the transaction interval to 5000 resulted in the same translation running 5.5% faster.Turning transactions OFF resulted in an improvement of either 12% or 19%.The performance advantages of changing the transaction interval or of turning transactions off will differ between various datasets.
For Esri Geodatabase, if possible, use the Transaction TypeTRANSACTIONS or NONEinstead ofEDIT_SESSION(Personal, File) orVERSIONING(ArcSDE).EDIT_SESSIONorVERSIONINGhave a significant impact on performance.如果这是你Geodatabase只需要这种模式 versioned or if you have certain custom behaviours or triggers (i.e.loading network topology, you have relationship tables, etc.).
You can also increase the speed of writing features bycreating all the feature datasets, feature classes, and tables ahead of timeso that the Geodatabase Writer only needs to open them, rather than create them.Try using an Esri XML Workspace Document as the Geodatabase template to create the entire Geodatabase before FME starts to write.
Make sure when you are updating, the update key field has an attribute index on it.
SettingSimplify GeometrytoNOwill speed up geometry writing.SettingValidate Features to Write to NOwill speed up writing features whose attributes are set to domain or subtype values.The values can be validated after the load using the Esri tools.
Avoid or minimize the number of annotation features, because writing to these is slow.It has been improved when writing annotations with no user-defined fields.
Only use as much precision and spatial resolution as you need.If all you need is 32 bit precision, set this on the writer feature type parameters instead of 64 bit.If all you need is decimeter level accuracy, don't use such a large scale factor that you are giving yourself 0.00001 mm accuracy.In both cases, you will be carrying around and processing more data than you need to.Reducing your effective precision and resolution should speed things up, especially for large datasets.Be forewarned that reducing your precision / resolution can cause problems with out-of-bounds errors or polygons collapsing into points if you don't give your data sufficient precision.
Note: Esri ArcSDE has beendeprecatedso this is no longer an option in newer versions of Esri products and FME
For the Esri ArcSDE writer, drop the spatial index andput the layers (spatial columns) into LOAD_ONLY mode.You can do this using SDE administrative commands via pre and post Python processing scripts .Before using the layers you'll need to build the spatial index.This operation can take a significant amount of time, but from a data loading standpoint, putting the underlying SDE layers into LOAD_ONLY mode can result in a very large difference in performance.Setting SDE_GRID{0} to certain special values can influence what grid type is created for a given DBMS which can affect performance.Refer to Esri ArcSDE documentation for more details (http://edndoc.esri.com/arcsde/9.3/api/capi/schemaobjects/layers/layerinfoSetGridSizes.htm) For the Geodatabase writers, set the grid 1 size to 0, doing this means that a spatial index does not get built during the load, but will automatically be built after the load completes.
Make sure your database writer is thefirst writer in the FME Workspace navigation tree(right click on the writer and use Move Up).FME caches the data for second & subsequent writers so having the database writer first ensures features are passed straight through to the writer.
In the reader parameters, if you don't require domain or subtype information then turn off the option for this information
Set a search envelope to reduce the number of features which will be read by the reader and passed into the workspace.The search envelope can be also be used to clip incoming features to further reduce the volume of data.This action is also performed at the database level so is further optimized for performance.
Check that the settings on the Geodatabase readerIgnore Network InfoandIgnore Relationship Infoare set to YES if you don't require Network or Relationship information to be read from the Geodatabase.There has even been found to be a performance improvement on reading feature classes with no network information when this setting is set to YES.
伟大的tips.I have a question.
With FEM 2016, is the ESRI ArcSDE Reader/Writer now called ESRI Legacy SDE?
@mjb4gisCorrect.The ESRI ArcSDE reader/writer is now called ESRI Legacy SDE.
How to Read and Translate all Feature Classes from Multiple Esri Geodatabases
Performing spatial queries on database tables using the FeatureReader
Reduce the size of Geodatabase workspace
Reading Basic Geodatabase Annotation - GDB to DWG
Working with Geodatabase Metadata: Writing/Updating Metadata
Comparison of FME readers and writers for SDE and Geodatabase
Writing ArcGIS Geodatabase Attachments
© 2020 Safe Software Inc |Legal