HelloZeroNet / HelloZeroNet/ZeroNet

Extremely sluggish propagation of the optional files to peers

Ouverte
#2,622 3 commentaires 1 réaction 0 personnes assignées Voir sur GitHub
Langage dominant
JavaScript
Étoiles
18.8k
Forks
2.3k
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

### Step 1: Please describe your environment

* ZeroNet version: rev4528
* Operating system: W10
* Web browser: FF beta
* Tor status: available
* Opened port: yes

### Step 2: Describe the problem:

Sorry for yet another whinning, but i have to as it seems like an issue that have to be fixed. I have published post on Millchan (famous zeronet site) with a few files attached (some were bigfiles no bigger than 10MB each)
Because i know how bad zeronet can sometimes be in seeding/downloading i have opened that poSt on three other servers each located in different location and each server has open poRt and clicked to seed all files of that post. In recent hours i was repeating the seed all request on that post on three servers as i was seeing servers has problems to download files of that post, only some files, some parts was downloaded. After around 6 hours like only half of the content was downloaded by my servers and it is not like all servers downloaded same parts, one has full file, other 0% of same file, etc. And it is just under 20MB total size of the files and my seeder connectivity is not bad + open port. That 3 servers hosts millchan and indeed maybe hundred/s of images/files on it while maybe another hundred/s of optional files are queued for download or being "paused" due to no peer.

On the host who published mentioned post, there is alot of content downloaded/uploaded. ZN directory has 5 million files and quite significant data transfer during previous hours. Zeronet is slow past years and swapping the computer after maybe 1-2 days of runtime. The CPU and HDD iops does not seem to be the bottleneck. If it is connection limit somewhere then zeronet users should be instructed (via ZN interface) to modify the limits or apply patch. If it can not be modified then zeronet should be supplied with the special browser that has no such limits.

Mentioned terribly slow propagation of the content is tragedy. Something has to be done about this so Zeronet can grow and people stay using it and do not giveup being too annoyed of the slowness. Thank you for the Zeronet, think about ways to allow it to go to the next level regarding performance.

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Piste de recherche

Commencez par reproduire le scénario de propagation de fichiers optionnels décrit pour ZeroNet rev4528, en utilisant les trois pairs, les ports ouverts et les quelque 20 Mo de fichiers indiqués ici. Aucun fichier source ni aucun test n’est indiqué ; suivez le chemin de seeding et de téléchargement des pairs afin d’identifier le goulot d’étranglement. Le travail est considéré comme terminé lorsque la propagation est sensiblement améliorée et que le comportement est couvert par un test de régression ou un benchmark documenté.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
javascript, python
Domaine
distributed-systems, networking, performance
Type d'issue
Bug
Difficulté
5/5
Temps estimé
Plus d'une semaine
Activité
À l'abandon
Clarté
À clarifier
Accessibilité débutants
18/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.