Playlist edit command is slower then playlist add command with large playlists

> For stored playlists the master data is in the playlist and I think the
> server reads it back. Might be wrong, but I think that's what's
> happening.

I haven't done any deeper investigation, but I think the main difference
is that commands dealing with the play queue ("now playing playlist")
have been optimized for performance, as they are being used all the
time. Modifying stored playlists otoh is a feature hardly anyone uses,
in particular not with larger playlists. Simply because editing
playlists in LMS is a pain to do. Therefore this code hasn't seen much
of optimization. As pippin mentioned there's a reason why playlists are
limited to 500 items by default...

Looking at the code I see that the edit commands still use the database
ORM layer on top of the database. This has been mostly replaced for the
play queue related commands for performance reasons.

--

Michael