Opened 12 years ago

Last modified 10 years ago

#8260 new Feature request

Force Priority Change

Reported by: vman2000 Owned by:
Priority: normal Component: FileZilla Client
Keywords: transfer queue priority Cc: leadacid@…
Component version: Operating system type: Windows
Operating system version:


If I have a bunch of low, large priority downloads in the transfer queue (using all the simultaneous connections) and then add a new item to the queue, setting the new item to highest priority I have to wait for one of the low priority items to complete before the HP item is processed (which could be hours).

It would be nice if there was a feature that allowed the more important item to be processed immediately rather than waiting for the trivial items to complete. Possible approaches might be:

  1. A 're-evaluate queue now' button/menu option. If newer item takes precedence over a current item then that current item is suspended until the new higher items are processed.
  1. Add a new ‘Force’ priority that just jumps to the top of the queue, either pausing a current download if required or possibly creating a new simultaneous connection (so temporarily increasing the number of simultaneous connections above the configured limit – probably best to limit to one forced item per queue in that case)
  1. Allow a current item to be manually suspended
  1. Just always re-evaluate the queue when a priority is changed.


Change History (2)

comment:1 by vman2000, 11 years ago

(Sorry, that should read 'large, low-priority downloads'!

comment:2 by Nathaniel Bezanson, 10 years ago

Cc: leadacid@… added

Just created an account to bump this.

Another use case: I set all my priorities before starting the queue, and with 2 simultaneous connections, the last of my high-priority files is slowed down because it's sharing bandwidth with low-priority files.

Ponder: Processing strictly in priority order (not starting a lower priority until the ones above are fully done) might make poor use of bandwidth in the case of small files. So what if that only happened for a gap of >1 priority level? Might be needlessly complex.

Note: See TracTickets for help on using tickets.