The QRP Empty column tells how many bits in the QRP routing sent by the remote client are zero. In LimeWire, these QRP tables are 64 Kbits, with 1 bit set per searchable keyword found in the shared files. If this table is empty (0%) there are no searchable keyword on this host (or no QRP table sent from it, if the QRP table size is shown 0KB, which means that this servent accept all queries and filters them itself before replying).

Generally, the higher the "empty" value, the best your UltraPeer will behave, as it will be able to not forward many queries to that remote leaf node. If a leaf node has a QRP table filled at 70% or more (30% empty or less), most queries will be forwarded to it, so QRP is not as much effective to limit the traffic to that remote host.

Note that for UP-to-UP connections, that now send each other a QRP table for the last hop, the QRP Empty level will grow with the number of leaf nodes that the remote UP supports and the total of files they share. It's not uncommon to see remote UP connected to you with the "QRP Table Empty" rate below 50%; this means that the QRP filtering optimization is not as effective as with higher values (commonly found with Leaf connections), but this still helps reducing the unneeded outgoing traffic (notably because most DSL and cable connections are asymetric and have a more limited available bandwidth for this outgoing traffic, and even a reduction of 10% will be helpful to maintain a lower usage for more responsiveness of your host).

QRP filtering is most effective for leaf-to-UP connections, simply because most leaf nodes do not share a lot of files, so they have a low percentage of QRP table filled (meaning a high percentage of QRP table empty). Previously this column was showing the *fill* level rather than the *empty* level now.

__________________
LimeWire is international. Help translate LimeWire to your own language.
Visit: http://www.limewire.org/translate.shtml