I have a total of 4 million records from various featureclasses stored in SQL spatial database and I have one workspace reading from SQL and writing out to an Esri FileGeodatabase (using API, not ArcObject writer). When I run this workspace in Desktop, it took approximately 16 hours to finish. However, it took 3 days to finish in FME Server. I checked the timestamps of the log in FME server, writing out was gradually getting slower and slower. I was just wondering why there is a significant difference between Desktop and Server with the same workspace?
Question
FME Server vs Desktop reading from SQL Server Spatial to Esri FileGeodatabase (API)
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+2Hi @kuanglee
I have a few questions about this situation. What version of fme workbench and server are you running? Where is the output gdb located in both cases? What are the specifications of each machine running fme workbench and server? Was fme server running other jobs at the same time on the same machine?
+1- Contributor
Hi @jlutherthomas
- 2017.1 for both FME Server and Desktop.
- server output to ...fmeserver/resources#/FME_SHAREDRESOURCE_TEMP and desktop output to my local folder.
- There was only one job running in FME server. Thanks.
+2Hi @jlutherthomas
- 2017.1 for both FME Server and Desktop.
- server output to ...fmeserver/resources#/FME_SHAREDRESOURCE_TEMP and desktop output to my local folder.
- There was only one job running in FME server. Thanks.
If you run the job again in FME Server does it take the same amount of time?
+1- Contributor
Hi @jlutherthomas
My desktop:
Windows 10 Enterprise; IntelXeon 3.5GHZ; 32 GB RAM, 64-bit OS.
FME Server: FME Server on Docker inside Ubuntu Server VMs.
Server Hardware:
Windows Server 2016
CPU: 2x Xenon e5-2620
RAM: 198gb RAM
Disk: 10k SAS drives not sure of the raid config
+2Hi @jlutherthomas,
Re-running caused the same amount of time.
Are you able to report a problem here.
If you could give us the workspace, data and a link to this thread that'd be really useful and an expert will be able to investigate.
+2Ok, I'm really not sure what's going on.
Are you able to report a problem here.
If you could give us the workspace, data and a link to this thread that'd be really useful and an expert will be able to investigate.