Have you set the writer-parameter "Features Per Request"?
Have you set the writer-parameter "Features Per Request"?
Hi @tomfriedl , yes, I added as many 0's as I could, just to make sure :)
sometimes less is more, the help writes:
Features Per Request
This parameter specifies the maximum number of features that may be present in a single write request to the server. This limit applies to Insert, Update, Delete, Upsert, and truncation. The writer will issue a request to the server whenever a single feature type accumulates the number of output features specified by this parameter.
Note: This parameter is only applicable when writing to an existing Feature Service. If the Feature Service was created in the same translation, then this parameter is ignored.
This parameter is useful for avoiding server timeouts or HTTP 500 responses that may result from long write operations.
If this parameter is not provided, it defaults to 1000.
sometimes less is more, the help writes:
Features Per Request
This parameter specifies the maximum number of features that may be present in a single write request to the server. This limit applies to Insert, Update, Delete, Upsert, and truncation. The writer will issue a request to the server whenever a single feature type accumulates the number of output features specified by this parameter.
Note: This parameter is only applicable when writing to an existing Feature Service. If the Feature Service was created in the same translation, then this parameter is ignored.
This parameter is useful for avoiding server timeouts or HTTP 500 responses that may result from long write operations.
If this parameter is not provided, it defaults to 1000.
Hi @tomfriedl Im not sure it will help adjusting, since I anyway gets an error when trying to write less features than what is specified. So I think I need to find a more neat way to write data in smaller groups.
sometimes less is more, the help writes:
Features Per Request
This parameter specifies the maximum number of features that may be present in a single write request to the server. This limit applies to Insert, Update, Delete, Upsert, and truncation. The writer will issue a request to the server whenever a single feature type accumulates the number of output features specified by this parameter.
Note: This parameter is only applicable when writing to an existing Feature Service. If the Feature Service was created in the same translation, then this parameter is ignored.
This parameter is useful for avoiding server timeouts or HTTP 500 responses that may result from long write operations.
If this parameter is not provided, it defaults to 1000.
Hi @tomfriedl ,
You were right. It worked fine adjusting the features pr request to 100. I think I just needed a few days to sink in what you actually suggested! ;)
I’m having the same error, even when I dial my process down to 10 features per request. Are there other processes that could be modified to improve this performance?
I was facing similar issue. Writer Mode to Asynchronous with Report Yes and Time Out 300 fixed this problem
Another is to use the FeatureWriter to do the same, but I would still need to do the setup for all the groups, so not sure if thats ideal.