# Howto Seed Swarm Service

- Example: How to create a seeder swarm with 5 xl-clients
    Step 1
  Stopp I2P
    copy the [rename me].war 5 times to i2p/webapps and rename the copies to
    xl-Leader.war ; xl-unit1.war ; xl-unit2.war ; xl-unit3.war ; xl-unit4.war ;
  Start I2P
    create somewhere a new folder and name it for example as xl-swarmstore1

-   Step 2
    copy the folder path into the textfield Swarm directory: of each client
    and press Save configuration

    Step 3
    for client xl-Leader select the checkbox-field Leader:
    and press Save configuration

    Step 4
    after of refreshing the browser for each client you can see that the leader of the swarm appears bellow the Swarm Service settings

    Step 5
    - copy your data-files to share in the folder xl-swarmstore1 you created in Step 1.
    - copy the torrent-files for the data-files in the folder xl-swarmstore1 you created in Step 1.
    - wait that the leader of the swarm finish the file checking.
    - wait that the swarmunits found the checked files.

    Step 6
    As example when you share a file with the leader and unit4 of the swarm then it looks like in the picture below
    you can see that all clients using only the leader proxy for communication with the tracker when you had selected the checkbox Use ProxyPort of Leader: like in the example above.
    That save some extra tunnels during a swarm sharing but you have to watchout that the leader is allways running or the clients get Tracker errors

    Appendix
    - only the swarm leader could removing files from the datastore for the swarm.
    - deleting the torrent file in the datastore for the swarm does removing the torrent from all swarm members.
    - a removed torrent needs to check again when you add it again.
    - a swarm can only have one leader.
    - every client has still it own datastore.
    - remove a client from the swarm by leaving the textfield of Swarm directory: emtpy and press again Save configuration .
    - never use a torrent that is in one off the clients private datastore listed too.

- Warnings: A swarm seed with 5 clients make only sense when you can share more than 100 kb/s
    and allocate the java enviroment of I2P with minimum 256mb at least.
    that you can do in the wrapper.config search for wrapper.java.maxmemory and change the value.

  When make it sense to use a swarm seed?
    - You can share at least more than 100 kb/s to I2P.
    - Your seed have less leechers. ( < 5 )
    - You are in superseed modus and want as fast as it is possible to share 100% of the parts.
    - Your seed is big sized.
    - Every client and it tunnels increasing the overhead. Sometimes it has more prosperity to using less clients to share effective more real datas.

  Some values
    - 0 - 5 Leechers -> swarmsize 2 - 4
    - 5 - 15 Leechers -> swarmsize 1 - 3
    - 15+ Leechers -> swarmsize 1 - 2

  Others: Superseed
    - switch on superseed and press "Reset" to fill the partlist with all pieces of the torrent.
    - run in superseed modus up 98% - 99% (superseed does that automatic and stopps when the piecelist count is 0).
    - switch off superseed and continuing as a normal seeder.
    that way you commit the torrent in 1/4 of time but at least it takes the usually same time before the first leecher completing the torrent. but with a higher chance even when the Firstseeder is offline for a longer term or meanwhile is sharing other torrents.

  Never run a swarm with autostart torrents!
  Allways use copies of your files!
  Swarm Service is a BETA-Release!

forum

copyright 2010 fwd Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported