They really do different tasks. SetiDriver is intended to run on a single PC and gives you the ability to cache WU's, some info on the WU being worked and an easy way to point the CLI client to a proxy server. SetiQueue is a proxy server which can serve multiple machines on a LAN or through internet connection. It too will cache WU's as well as track all sorts of stats concerning the clients that fetch or flush through it. Neither one gives you an inherent ability to process a WU faster. It is common to run SetiDriver and Seti Queue on the same machine, Seti Driver fetches and flushes through Seti Queue, and Seit Queue fetches and flushes to Berleley, Orange Kid or wherever. SeiQueue has better ability to manage the WU's in your cache, but deleting VLAR's is not a popular practice because somebody has to do them.