Append with Transformation to AGO Slowwwwww

[ToddPlank2]

Is it typical for Append with Transformations to operate so slow when pushing data to a solution feature layer in AGO?

Have a dataset with 2900 records, nothing out of the ordinary, that will take most of the day to upload.  Upload network connection is fast, 400Mbps upload,

[TedHoward2]

Does your source data contain attachments? That can cause performance to suffer significantly. It has to do with the way geoprocessing tools are currently architected. Improving support/performance in DLT for feature services is a priority item for an upcoming release.

[ToddPlank2]

No attachments

[Scott_Stopyak]

I'm trying to run the tool on a small county worth of parcels with very minor transformations. Most of the fields map directly in. Maybe three are concatenated addresses or owner fields. It has been running for a couple hours. The data source and destination are local. It might not be that uploading to a feature service is the bottleneck. Maybe it is the tool itself that is super slow. A regular append with field mapping would have been done by now I think. Do you get similar run times with a local destination?