MOD Kommentare... (3.0 / 5 Punkten (463)
Board: Fragen und Hinweise: eMule SDG-PoWa.MoD-Forum...
eMule SDG-PoWa.MoD Download Archiv...
Features found in Pawcio's mod and also in SDG-PoWa:
Completely new upload/download system. For details look below (after list of
Features for RELEASERS:
Powershare was designed for releasing files (extended version from Morph XT). If
one file is being powershared it will be the only file that is being uploaded.
Like that a releaser of a new file doesn’t have to unshare all other files to
achieve the same behaviour. PS is a powerful tool but it should be used
correctly to avoid problems. That’s why there are several modes for PS:
If PS is deactivaed by default it is still possible to powershare some files in
the Shared Files section through the context menu.
PS is activated by default.
In this mode PS will decide itself if there are enough sources around or if the
file should be powershared.
You can set a limit for PS. You can do this also in the Shared Files section. If
The Mod detects as much complete sources as you’ve entered as limit then it will
deactivate PS for that file.
Overshares Before Hiding Chunks and Share only the needed:
These features are especially interesting for releaser. They allow them to say
how many times a chunk should be uploaded. When a chunk has been uploaded as
often as specified it will be hidden for other users. This behaviour results in
an efficient spreading of chunks in the network. In these mods HideOS is
improved so chunks are hiden only when user is downloading data and unhiden just
before ending of transfer.
Use Smart Selective Chunk Sharing:
This feature analyzes for every file which chunks are popular in the network and
which are rare. It will priorize the rare chunks as long as they are considered
rare and upload them more often than popular chunks.
Anti Hide OS
This feature analyzes which chunks are hiden by remote clients and allow proper
calculation for ICS and WebCache feature.
NOTE: in SDG-Powa, the Powershare is only allowed with complete files
From WebCache mod, allows eMule to use the http-proxy of the ISP to cache file
parts, which can be downloaded by several users with full speed from the proxy.
+ Much higher download speeds.
+ Some/most ISPs do NOT count traffic from their proxy server for the monthly
+ Less waste of upstream bandwidth.
+ Less waste of traffic for your ISP and the internet as a whole.
+ Less negative influence from Leechers.
+ Smaller queues (less waiting).
+ Principally better, because wasting is... well... a waste.
+ It's an add on: eMule remains backwards compatible and only uses http file
transfers when it chooses to do so.
(as an option in "Extended Settings" - "Pawcio Credits"):
- Range from 1.0 to 100.0
- Multiplier of 3 (instead of 2) ---- ratio = 3 * downloaded / uploaded
- For new clients (downloaded and uploaded data less than 1MB) ratio = 3.0 (instead
- If you have recieved more than 1MB from someone but haven't given anything
back user gets ratio = 10.0 * recieved in MB (but not more than 100.0)
- Small bonus for clients that have given you many MB:
- if you get 100MB then user recieve ratio = 50.0 till you give back 108MB
- 50MB - ratio = 25.0 - 55MB
- 25MB - ratio = 12.0 - 28MB
- 9MB - ratio = 5.0 - 12MB
Transfer Clients Window:
Transfer Window. Now You Can See Who Is Uploading To You and other information
such as speed and progress of your download in real time.
Modified Tray Menu:
Tray menu from eMule Plus mod with fast access to Upload Speed Sense (USS) and
Download Speed Sense (DSS) options.
In almost all windows you will be able to see a list of the client that you are
interacting with. This addition will allow you to view what emule mods people
are useing, Otherwise you would only be able to see the standard client name.
USS and DSS options now in Scheduler
Found in Preferneces -> Scheduler.
Configuration of MSS in Connection Tab
(from Morph Next and LSD mod)
Inteligent Chunk Selection
From enkeyDev! To avoid two or more users choose to download the same chunk, ECS
relies only on randomness: users choose randomly *hoping* to choose a different
chunk each; in ICS users exchange infos about what chunk is being downloaded
ATM, then a user can choose the less-downloaded (priority: spread the file
faster); in ICS the user preference "first/last chunk" take importance only when
there are NO rare chunks (priority: spread the file); With ICS, the same
situation is a release-mode one, then you will choose the shortest-to-complete
chunk that is not being downloaded ATM by any other client. This increase the
probability you and the other clients would have downloaded different chunks and
keep (globally) a complete source for the file, though a couple of sources quit...
Pawcio Bandwidth Control (Tag: "Pawcio: BC") - tab "Bandwidht Control" in
Completely new upload/download system based on Maella (50 ms, packets splitting),
ZZ (USS), and own ideas (DSS, ...) .
A. Special algorithm for minimalization of opened slots (as an option: can be
turn on/off by "Minimize number of opened slots" option)
B. Bandwidth Setting in 0.1 kB increments (Maella idea)
C. Simplified options for USS and DSS(now you have to choose only the minimal
upload/download and decide how much eMule should use your bandwidth - slider -
no more need of % of lowest ping)
D. Advanced option for USS and DSS (you can exactly choose what max ping should
be and which server to ping)
E. Auto management of Max Connections and Max Connections per 5 seconds. If you
set them too high BC can detect this(auto management can be turn on/off by
Manage of active connections)
Info: BC changes only too high settings (when management is turned on), if they
are reasonable, they won't be changed
F. Pinging through UDP thanks to Dong, so if your ISP is blocking ICMP traffic
you can select "UDP Ping" in "Bandwidth control" tab and it should work (you
need to open UDP outgoing port (default 33434) and have administrative right in
Windows NT and XP pro). If UDP sending can't be used BC will automatically move
on ICMP version.
G. Possibility of "catching" whole eMule upstream/downstream within specified
--> I: eMule protocol, IP, TCP, UDP header overhead (option "Include Overhead")
--> II: TCP connection negotiations (option "Include connections overhead") -
--> III: TCP acknowledge packets (option "Include TCP Ack") - empiric (doesn't
not take account of RWIN size - only 2.5% of stream)
H. Cumulate upload bandwidth to certain slots (as an option - "Cumulate
Bandwidth for upload slots") - idea of ZZ:SlotFocus
I. "Session up: down 1:4 limit" from Morph Next.
J. Status of USS and DSS (working, preparing, etc) and all limits (up, down) can
be seen on Bandwidth Control Tab (you can enter any value in Connection tab but
limits of ratio are preserved, you can see them on Status on Bandwidth Control
K. There is new type of clients: Clients on reserved upload list (ready in any
time to start upload):
--> - when "Minimize number of opened slots" is not selected, reserved client is
added when client on upload queue is just ending its session (so reserved client
is able to prepare before taking the freed slot - no delays)
--> - when "Minimize number of opened slots" is selected, there is quantified
number of reserved clients (algorithm in CUploadQueue::AcceptToReserve)
--> - when "Cumulate Bandwidth for upload slots" is selected, reserved clients
are very similar to Trickle Slots in ZZUL (so there is rotation between upload
queue and reserved upload queue)
L. Yellow lines added to graphs (in Statistic Window) showing whole current
upload and download (with whole overhead)
Badwolf's upload managment
Keeps some Tricky slots opened ( 3 for limits over 10K, 1 for less) too as a "buffer"
when a fast upload finishes to redistribute the bandwith left free. Allows to
maximize your average upload rate.
Time between send/receives:
Old eMule (before ZZUL including) has got value 100 for both upload and
download. Now official eMule has 1 for upload and 100 for download. Old BC
version has 50 for both. Higher value means lower CPU usage, but a bit worse
control of bandwidth. So if you experience a bit high CPU usage you can increase
those values. As written above old BC (e.g. in Pawcio 4) has got 50 for upload
When "Include connection overhead" is selected you have to set minimum 11kB/s (instead
of 10kB/s) for upload limit to have unlimited download, and minimum 3.5 kB/s (instead
of 3kB/s) to have 4x ratio.
When "Include TCP Ack" is selected Session up:down ratio (ZZ:RATIO from
MorphNext) is forced. All limits you can see on Status - Bandwidth Control.
Description of "Bandwidth Control" tab:
USS (Upload Speed Sense) DSS (Download Speed Sense):
USS (work of ZZ) and DSS dynamically finds current, best upload/download 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
rarely) 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 compare with received response from host, this
value is "Max ping allowed". It would be the best if you could know what proper
ping for your connection is (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 -
Minimize number of opened slots: when this option is selected eMule will open
fewer slots than original if it is possible (if fewer 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
different) - 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 whether he has slow or
fast connection) and then rest bandwidth gives for the fastest users (faster
spread of chunks). Priority client is always client who 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 communicates 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 connections overhead: not only eMule communicates between users, system
and network layer also (on different 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 changed:
- 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 /
Successful / Failed.