Skip to end of metadata
Go to start of metadata

BitTorrent download info

  • tracker version: 4.4.0
  • server time: 2013-01-28 10:14 UTC
info hash torrent name size complete downloading downloaded transferred
51f3f57d06f90ae7479e66ba28b8be6f7bc8c6c4 EeeDora_2008-06-23_01h15m 330MiB 1 0 60 19.37GiB
94da22f456c040a08cac267898d24f831967a3bf SmartOS_tgz-20130125T031721Z 147MiB 3 0 9 1.29GiB
fdad7f1e5d63b0a4f8d531d7b21062ff71e391c0 smartos_platform-20130111T010112Z.tgz 145MiB 0 0 4 583MiB
  3 files 624MiB 4 0 73/76 21.24GiB
  • info hash: SHA1 hash of the "info" section of the metainfo (*.torrent)
  • complete: number of connected clients with the complete file
  • downloading: number of connected clients still downloading
  • downloaded: reported complete downloads (total: current/all)
  • transferred: torrent size * total downloaded (does not include partial transfers)

This was a first test to verify what is need to .... improve network experience.

A slight increase from previous.

The reason I started to get a look at SmartOS is that my old server is from Centos 4 days. Currently running Centos 5.9.
It's getting old and the requirements that I have has increased and is more diversified  than before.

Family is more one the move and involved in different activities that need to be synced. Android phone and mobile data is new.
My neuro/brain science work and neurorehab makes me more mobile.

New hardware => New System to support people and organizations on the move.

SmartOS seem to be flexible enough.

Downloading SmartOS is slow at best and compared to downloading a ISO of Centos using BitTorrent.

I can download a DVD ISO at a speed of 50-60 Mbit/s if I monopolize and don't throttle.

It's a good system test.  Our firewall can handle about 80-95 and the back-haul links/radios handles 300Mbit/s. It's a shared connection so throttling is advised.

I run several system and  with current handling regular updates is using a lot of bandwidth. It's the some data repeated all over but sourced from different mirrors i.e no proxy cache to save bandwidth and  time.

Can this be improved by using peer2peer and some small changes to existing update mechanism ?

I use a agile incremental and integration driven method (wikipedia: system_anatomy project_anatomy) with own adaptions to create a flow of continues changes taking a step at a time.

First step is Download SmartOS using BitTorrent.

bittorrent bittorrent Delete
anatomy anatomy Delete
agile agile Delete
agility agility Delete
integration integration Delete
driven driven Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Jan 28, 2013

    Perhaps if part of the release process were to simply create a tracker & magnet link, and use the actual ftp/http authoritative source as a web seed. I'm actually quite surprised that more OS distributions aren't leveraging this. Bonus points to add said magnet & tracker links to an RSS feed so as to facilitate an instant swarm upon every release.

  2. Jan 28, 2013

    I'm not sure about web seed, I did a try run using web seed and didn't success to get the tracker established to form a swarm.

    In the end the transport has to be integrated in the release process and also in img pkg update. So every update can contribute to the swarm.

    There are mechanisms that might be interesting like Apache artifacts repository

    A step wise approach and let the mechanisms evolve may be result in some new thinking.

Add Comment