Someone will surely give you profiling tips. I personally would like to know which function starts the save operation, and then use the Emacs debugger at the moment the save starts - either add (debug) immediately before the general save operation, or use Mx debug-on-entry for the function that initiates the save.
I would go through the debugger (using d and c ) to find out what this laborious step is. If I were to guess blindly, I would suggest that some applications at the level (for example, related to python) massing / converting or checking stored data occurs before the actual disk is written.
Among other things, this will give you a better idea of ββwhat is happening and why.
source share