Talks: Difference between revisions

From CSCWiki
Jump to navigation Jump to search
Line 28: Line 28:
* citric-acid (250 Mbps)
* citric-acid (250 Mbps)


The list of mirrors can be found in /var/www/mirrors.txt the web server selects a random mirror from this list at each file request. We now run [[SNMP|Net-SNMP]] on all of our hosts, so we have real-time access to network and cpu load data. We should therefore be able to write a more intelligent mirror selection script. We also use mirror.cs to mirror on-campus.
The list of mirrors can be found in caffeine:/var/www/mirrors.txt the web server selects a random mirror from this list at each file request. We now run [[SNMP|Net-SNMP]] on all of our hosts, so we have real-time access to network and cpu load data. We should therefore be able to write a more intelligent mirror selection script. We also use mirror.cs to mirror on-campus.


We are currently looking at [[QoS|QoS tagging]] to reduce the load on campus switches/routers.
We are currently looking at [[QoS|QoS tagging]] to reduce the load on campus switches/routers.

Revision as of 00:37, 15 January 2008

Requested

  • Michael Geist
    • Canadian Law and Technologist Blogger
  • Wayne Beaton
    • Technical Evangelist for The Eclipse Foundation
  • Keith Packard
    • X Windows
    • Holden has contacted him again to ask him to come in October
  • Walter Bright
    • D Programming Language
  • Hans Peter Anvin
    • Linux kernel hacker
  • Cory Doctorow
    • Co-editor of Boing Boing
  • CSCF/MFCF/IST Open Forum
    • Dave Gawley [CSCF]
    • Dawn Keenan [IST]
    • Jim Pell [MFCF]
    • Stephen Mann [SCS]
    • Bruce Campbell [IST]

Encoding

We use dvgrab to rip the talks from the camera and ffmpeg to encode.

Mirrors

  • taurine (90 Mbps) [It can probably push much more if it were on a gigabit link]
  • citric-acid (250 Mbps)

The list of mirrors can be found in caffeine:/var/www/mirrors.txt the web server selects a random mirror from this list at each file request. We now run Net-SNMP on all of our hosts, so we have real-time access to network and cpu load data. We should therefore be able to write a more intelligent mirror selection script. We also use mirror.cs to mirror on-campus.

We are currently looking at QoS tagging to reduce the load on campus switches/routers.