-
Notifications
You must be signed in to change notification settings - Fork 13
Open
Description
Hi, I observed that some json responses can get really huge really fast. Dealing with deluge instance containing lots of items generates in my case 2MB json response sending to client every 2 secs.
While it's not a big deal when using server-client locally it can be serious performance issue.
What do you think about implementing some performance improvements like:
- instead of dealin with plain json data, compress response servers-side and uncompress client-side. Those data is highly compressible.
do some basic filtering server-side - for example when use filter only for Active or Downloading or Paused items return only items matching those criteria instead of sending whole list- reduce response size by removing unused parameters like, "Peers" / "Files" / "FileProgress" / "FilePriorities" and many more that are not used for data presentation.
Edit: point 2 removed it already works that way (filtered by deluge daemon)
Metadata
Metadata
Assignees
Labels
No labels