太好了，真的能遇上高手。
有关lsd中各种特殊设定的作用，正好手头有些资料，不过是英文的。
**LSD Tweaks**
LSD tweaks I:
-Disable AutoSort: disables AutoSort queue (saves CPU usage)
-Reconnect on lowID: eMule reconnects if user has a lowID.
-Increase release priority: Option to Increase Release Priority, pushing to 1st position queue (Very good for rare/small files)
-Use old priority system: old priority system uses different credit modifier then new eMule versions (from 0.27a and up = new priority system!), for more info about the credit modifiers see the eMule FAQ "rating&score" section.
-Disable/Enable [XS] Exchanged Sources Between Clients.
-Force Drop NNS (not needed source): drops from queue this source has he has no parts you need at the moment, note that this user may have them later on.
-Force Drop Full Queue (FULLQ): drops from queue this source as his upload queue reached its max and have no room for new user, this source may have room for you later.
-Force Drop Unknown: drops unknown sources (sources with status Unknown are dead/timed out sources or if you are banned and other unknown situations).
-Disable Re-Ask NNS: disables the re-asking of NNS in the set interval.
-Disable Re-Ask FULLQ: disables the re-asking of FULLQ in the set interval.
-Disable Re-Ask Server: disables the re-asking of server for new sources in the set interval.
-Frequency of Auto A4AF (af4f=ask for another file), time interval for A4AF may be altered here.
-Uploads Slots:
-Uploads Min: user defined minimum number of upload slots for better control of bandwidth distribution.
-Uploads Max: user defined maximum number of upload slots for better control of bandwidth distribution.
-Max New Connections in 5 sec抯: This is the number of new connection's eMule opens during 5 seconds. Default is 20.
-Max UDP Per File: When this limit is reached eMule stops asking servers for sources except the one it is connected to. Further sources are gathered via Client to Client Source Exchange and the local server.
This value depends on the Max Sources per File setting. 10-20% of Max Sources should be fine. As this limit greatly helps to reduce the load on servers it shouldn't be set any higher than 100.
-Max Sources Per File soft limit: On Soft Limit eMule stops searching for sources via Client to Client Source Exchange and on all servers. Only sources from which users are directly connected to for up- or downloading are added until Hard Limit is reached. Soft Limit cannot be changed as it is calculated from Hard Limit
-Hard Limit: Hard Limit is the maximum number of sources allowed for a file. If this limit is reached eMule stops accepting sources for this file.
-Max Connections: This is the maximum allowed number of TCP/IP and UDP connections. Connections are only opened if there is data transfer in progress, for search and queue requests or Client to Client Source Exchange.
Altering this value is normally not necessary, except on Windows 98/ME, then don't set this value any higher than 50.
-In LSD tweaks there are 2 buttons default/optimal, default gives standard settings, optimal is recommended but not good for all internet connections.
Basic recommended settings. (by drLSD):
max soft: 2000/3000
max hard 3000/4000
udp:100/200
max con 5: 60/100
Total con: 20000+
-Soft/hard if put higher can cause high-CPU usage or slow speed.
-It is not recommended downloading at the same time more than 3 files with 4000 sources.
LSD Tweaks II:
MSS (Max Segment Size): (SiRoB/mighty knife)
This setting can lower the IP overhead.
Don't confuse IP overhead with eMule overhead, the second one is shown by eMule if you activate "Show overhead bandwidth".
Actually, you will have less IP packets send for the same amount of data (less TCP-IP headers and more data). So, the transfers will be optimized.
To know what is the best MSS for you, go to the URLs shown in the "LSD tweaks II" links in preferences.
LSD mod **main features**
Source management: (dr-LSD)
Disable Source Exchanging between clients: You won't send and receive sources from other clients (keep this unchecked, except if you have a very small connection).
Disable NNS re-ask time: You won't re-ask files in NNS (Not Needed Source -> sources that don't have the chunks you need) status. If unchecked, you can set a time for re-ask.
Disable Full Queue re-ask time: You won't re-ask files in Full Queue status. If unchecked, you can set a time for re-ask.
Disable Server re-ask time: You won't re-ask the server for new sources. If unchecked, you can set a time for re-ask.
Upload Slot control: (dr-LSD)
Can adjust min slots to 1-16 and Max slots x-150
this feature gives the user control on how many upload slots will be open, so users can control how to distribute their bandwidth.
Release file control (dr-LSD)
Move "Release Files" to 1st queue position. (on/off)
Save/Load Sources 2 (enkeyDEV/kei-kun/Ottavio84)
Activate/deactivate it on the "Extended Settings".
This function save sources (10 by default) for the files that have less than a determined number of sources (300 by default).
If you restart eMule, these sources won't have to be searched again.
A4AF (Asking For Another File) control: (from enkeyDEV)
With eMule/eDonkey, you can't ask a client for 2 different files. The status of one of the file is set to A4AF.
Swap all A4AF to this file auto: If you ask for 2 files from the same client, this function automatically download from the file that has the box checked.
Swap all A4AF to this file now: Same as before, but not automatic.
Swap all A4AF to any other file now: You can guess.
The first number of the source's count is the number of files in A4AF status.
AntiCreditTheft: (from lovelace)
Detect if 2 people use the same userhash and remove the userhash thief (and their credit) from upload queue.
MSS (Max Segment Size): (SiRoB/mighty knife)
This setting can lower the IP overhead.
Don't confuse IP overhead with eMule overhead, the second one is shown by eMule if you activate "Show overhead bandwidth".
Actually, you will have less IP packets send for the same amount of data (less TCP-IP headers and more data). So, the transfers will be optimized.
To know what is the best MSS for you, go to the URLs shown in the "LSD tweaks II" links in preferences.
Description made by Pawico at the official Board:
Description of "Bandwidth Control" tab:
USS (Upload Speed Sense) Group:
USS (work of ZZ ) and DSS dynamically finds current, best upload/downlaod rate from the range of "Min upload/download in kB/s" and "Max upload/download in kB/s". "Max upload/download in kB/s" can be found automatically by selecting "Auto" box. USS/DSS lower the upload/download when other applications are using your connection or when mule is downloading very fast (lowering upload - important for ADSL user when download can be limited by upload). The key of USS/DSS to work is pinging a host. SS can find the proper host to ping for you (just select "Auto" box, on the right of "URL/IP to ping:" input box). If searching fails (very rearly) it uses host given in "URL/IP to ping". If you know which host to ping
unselect "Auto" box and input own address. By pinging, USS/DSS gets replies from host and on this basis it knows what to do (increase or decrease current upload/download). USS/DSS has to have a value to comapre with received respons from host, this value is "Max ping allowed". It would be the best if you could know what is proper ping for your connection (if you know, then select "Max ping allowed" box and input it). If you don't know, do not select "Max ping allowed" box, instead use intuitive slider above (it will find the proper ping for on the base of lowest ping calculated during preparation of USS/DSS). When you move slider on the left upload/download will be lower but you can surf the net easily, on the right - opposite behaviour.
Minimize number of opened slots - when this option is selected eMule will open less slots than original if it is possible (if less users can take more bandwidth). It means that the chunks will arrive faster to users.
Cumulate bandwidth for upload slots (idea of ZZ: Slot Focus - but a bit diffrent) - when this option is not selected eMule tries to upload to all users on upload queue with the same speed. Selecting this option is causing that eMule always upload to one user (Priority client - no matter wheter he has slow or fast connection) and then rest bandwidth gives for the fastest users (faster spread of chunks). Priority client is always client which was first on upload queue (stayed the longest), thanks to this for every client ("fast", "slow") will be a turn to get data.
Session up:down limit (1:4) (idea of ZZ, changed by MorphNext) - instead of 1:3 and 1:4 ratio for download (or unlimited when upload higher than 10) there is limit 1:4 for session. As long as you have downloaded less than 4 times the amount you uploaded (or you are uploading higher than 10kB/s) the limit of download is the same as value entered in "Connection tab" (so it can be unlimited). When you have downloaded more - the download is limited to preserve 1:4 session ratio.
Include overhead - eMule upload not only file data. It comunicates with other users (queue ranks, names of files, hashes, etc), server. If you want this upload/download can be included within limits defined in "Connection" tab or USS/DSS.
Manage of active connection - when this option is selected and you have too high values of "Max connections" and "Max connections per 5 sec for your connection, they will be adjusted automatically when needed.
Include connection overhead - not only eMule communicates between users, system and network layer also (on diffrent level). This system communication can take a lot of bandwidth especially when sorces are loaded (SLS system, or a file with a lot sources from server). It's almost impossible to calculate this overhead exactly, but an approximate is acceptable. You can include this overhead within upload/download limits (USS/DSS or "Connection tab"). Keep in mind that to have the unlimited download or 1:4 ratio with this option selected the limits for upload were chaned:
- unlimited download needs minimum 11kB/s upload instead of 10
- 1:4 ratio needs minimum 3.5 kB/s upload instead of 3
Include TCP Ack Packets - every data received needs to be acknowledged (it is TCP ACK packet), so it's generating upstream. The amount of overhead is hardly to calculate exactly, it depends on many settings (e.g RWIN). But as with "Include connection overhead" some approximation can be done (64kB/s downstream needs circa 1.5kB/s upstream). You can include this overhead within upload limits but then Session up:down limit (1:4) is enforced.
Status Group:
Here you can see what's happening with USS/DSS, what are the limits of download (limited by settings described above - so you don't have to calculate them) and what host is pinged. USS/DSS can be Disabled / Preparing / Succesfull / Failed.
The original thread can be found here:
Pawico-Mod thread @ official Board （
http://forum.emule-project.net/index.php?showtopic=29351）
