Intelligent chunk selection
| (6 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| − | With Intelligent Chunk Selection users exchange | + | With Intelligent Chunk Selection users exchange informations about which chunk is being downloaded at the moment, then a user can choose the less-downloaded (priority: spread the file faster). |
| − | + | Abbreviation: ICS. | |
| − | In ICS the user preference "first/last chunk" | + | In ICS the user preference "first/last chunk" catches only when there are no rare chunks (priority: spread the file). |
| − | In release | + | In release mode, the shortest-to-complete chunk that is not being downloaded at the moment by any other client is selected. |
| − | This | + | This increases the probability you and the other clients download different chunks and keep (globally) a complete source for the file, even if a couple of sources become unavailable. |
| − | * | + | * You get a detailed view of parts spreading with double click on file in shared files window |
| − | There are | + | There are three possibilities: |
| − | * RELEASE : complete | + | * RELEASE: complete sources <= 3: priority to upload/download the rarest chunks |
| − | * SPREAD : complete | + | * SPREAD: complete sources between 4 and 10: small chunks first, rare chunks later |
| − | * SHARE : complete | + | * SHARE: complete sources over 10: normal behaviour (ECS or first/last) |
| − | |||
| + | ==== enkeyDev's explanation ==== | ||
| + | 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... | ||
| − | [[ | + | - Detail view of parts spreading with double click on file in shared files window |
| + | |||
| + | |||
| + | by enkeyDev. | ||
| + | |||
| + | ==External links== | ||
| + | * [http://forum.emule-project.net/index.php?showtopic=13623] [patch] Intelligent Chunk Selection As in enkeyDEV.5 mod | ||
| + | |||
| + | [[Category:Features]][[Category:StulleMule features]][[Category:MorphXT features]] | ||
Latest revision as of 15:29, 17 August 2010
With Intelligent Chunk Selection users exchange informations about which chunk is being downloaded at the moment, then a user can choose the less-downloaded (priority: spread the file faster).
Abbreviation: ICS.
In ICS the user preference "first/last chunk" catches only when there are no rare chunks (priority: spread the file).
In release mode, the shortest-to-complete chunk that is not being downloaded at the moment by any other client is selected.
This increases the probability you and the other clients download different chunks and keep (globally) a complete source for the file, even if a couple of sources become unavailable.
- You get a detailed view of parts spreading with double click on file in shared files window
There are three possibilities:
- RELEASE: complete sources <= 3: priority to upload/download the rarest chunks
- SPREAD: complete sources between 4 and 10: small chunks first, rare chunks later
- SHARE: complete sources over 10: normal behaviour (ECS or first/last)
enkeyDev's explanation
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...
- Detail view of parts spreading with double click on file in shared files window
by enkeyDev.
External links
- [1] [patch] Intelligent Chunk Selection As in enkeyDEV.5 mod
