span8
span4
span8
span4
My colleague and I have both an FME license.We use a workspace to bound pictures (jpg) to trackpoints from a gps (gpx) based on their time.
When he runs the workspace it takes about 10 minutes for 5000 pictures.
When I run the workspace it takes about 10 minutes for 100 pictures.
Our pc's are both very good.Similar cpu's (i7 5930).I have 64gb ram.He has 32 gb ram.I have a nvidia quadro K4200.He has a gtx 1080.
SOLVED - thx for the input guys.
It was much easier.I was running my workbench with full inspection and my colleague wasn't.
I guess i'm still a noob :)
Feature Caching is ONThe workspace may run slower because features are being recorded on all connections and ports.Though you'll have to have a keen eye,as it races past as it's on lines 2 and 3 of the log!
- Make sure both have 64-bit FME installed.
- Make sure both use an SSD as temp disk
- Make sure the network-connection to the jpeg-files are through the same fast network.Try to copy the files locally and then run the workspace with all files locally to see if it is faster.
We both have FME 2017.1.2.1 and both have SSD's.
my log:
Translation was SUCCESSFUL with 7 warning(s) (0 feature(s) output) FME Session Duration: 12 minutes 49.8 seconds.(CPU: 261.8s user,478.3s system) END - ProcessID: 9340,peak process memory usage: 16702200 kB,current process memory usage: 202956 kB Translation was SUCCESSFUL
Are you running the exact same FME version?
Does perhaps one of you have an SSD disk,an the other not?
At the end of the execution of the workspace the log window contains a synopsis of memory used etc.Could you please post it here.
© 2019 亚搏在线Safe Software Inc |Legal