Skip to main content
Question

The first request is slow- fmeserver uses 5 seconds to find the reader

  • April 8, 2018
  • 1 reply
  • 10 views
bjarne
Contributor
Forum|alt.badge.img+5

Fmeserver uses longer time for the first request. If a workspace is run several times it takes less than a second, but the first request is slow. It can take more than 5 secods to creating the reader:

2018-4-8 16:07:39 | MULTI_READER(MULTI_READER): Adding MSSQL_SPATIAL Reader with keyword MSSQL_SPATIAL_12018-4-8 16:07:39 | Using Multi Reader with keyword `MULTI_READER' to read multiple datasets2018-4-8 16:07:44 | Creating reader for format: Microsoft SQL Server Spatial

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.

1 reply

J
Forum|alt.badge.img+2

Hi @bjarne

The FME Server engine likely will load things the first time round, then caches it so the second, third time etc it's a lot faster.

Each FME Server engine restarts after 100 successful transactions or 3 failed ones by default, so you may see this happen from time to time depending on where the engine is in that cycle.

Community Stats

32,060
Posts
121,724
Replies
39,688
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.