No problem! No, I haven't heard of this problem before. If creating the portal fails, it should delete the db directory and any other files/folders that were created during that process. Perhaps it couldn't delete the directory when it tried to? The logs should tell you why it failed and hopefully why it couldn't delete the db folder.
... View more
Remember that when the processing is on the server, it means the data must also be on the server, so it will take some time to serialize and upload data from ArcGIS Pro to the server prior to the service actually running. These services are typically meant to run with smaller sized data sent from the client, but executing against larger datasets on the server. For example, if you have a Viewshed service, the server can store the DEM (the bigger dataset) and the client can sent simple points, and return the viewshed for those points. Services that would take both the DEM and the points as input from the client should be fine for smaller cases, but if the user is sending a big DEM up to the server the whole thing will be quite slow. If you have questions about how to design the geoprocessing service for best performance, take a look at the following topics: Performance tips for geoprocessing services—ArcMap | ArcGIS Desktop Large dataset upload and download considerations—ArcMap | ArcGIS Desktop This is one advantage that the Standard Feature Analysis tools also provide - they primarily use data that is already located on the server or in the enterprise as input (web feature layers, etc.), so the processing doesn't need to move data around.
... View more