Save of Tile data (and most likely Resource data) can be very slow #123
Description
I've experienced this slow down on a small PIR dataset locally with only 1500 resource instances.
For example, saving a tile from a "Provenance Activity" resource instance took almost 10 seconds. There were about 275 instances of that type in the dataset I was working with.
The endpoint it was hitting was:
http://localhost:8000/api/tile/provenance/name/acf26b9b-e728-4033-8564-a38b32beb4df
you'll have to replace the tile uuid at the end of that url and replace it with a valid uuid from your local instance
On the other hand, with that same dataset and working with a model with only one instance, the save seemed much faster (less than 1 sec).
For point of reference the current editor POSTs data to the tile endpoint and returns in less than 1 sec.
You can see this by opening the current resource editor and saving the same tile (card).