Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Scaling Science
Search
Matt Wood
November 21, 2012
Science
3
460
Scaling Science
Introducing five principles for reproducibility.
Matt Wood
November 21, 2012
Tweet
Share
More Decks by Matt Wood
See All by Matt Wood
Field Notes from Expeditions in the Cloud
mza
2
360
A Platform for Big Data
mza
6
720
The Data Lifecycle
mza
5
480
Provision Throughput Like a Boss
mza
0
410
Impact of Cloud Computing: Life Sciences
mza
2
820
Latency's Worst Nightmare: Performance Tuning Tips and Tricks
mza
4
1.1k
Under the Covers of DynamoDB
mza
4
980
From Analytics to Intelligence: Amazon Redshift
mza
9
960
High Performance Web Applications
mza
6
600
Other Decks in Science
See All in Science
いまAI組織が求める企画開発エンジニアとは?
roadroller
2
1.4k
事業会社における 機械学習・推薦システム技術の活用事例と必要な能力 / ml-recsys-in-layerx-wantedly-2024
yuya4
4
290
拡散モデルの原理紹介
brainpadpr
3
5.8k
ICRA2024 速報
rpc
3
5.9k
はじめての「相関と因果とエビデンス」入門:“動機づけられた推論” に抗うために
takehikoihayashi
17
7.2k
Improving Search @scale with efficient query experimentation @BerlinBuzzwords 2024
searchhub
0
270
LIMEを用いた判断根拠の可視化
kentaitakura
0
430
構造設計のための3D生成AI-最新の取り組みと今後の展開-
kojinishiguchi
0
860
Coqで選択公理を形式化してみた
soukouki
0
280
白金鉱業Meetup Vol.16_数理最適化案件のはじめかた・すすめかた
brainpadpr
3
1.4k
02_西村訓弘_プログラムディレクター_人口減少を機にひらく未来社会.pdf
sip3ristex
0
120
The thin line between reconstruction, classification, and hallucination in brain decoding
ykamit
1
1.2k
Featured
See All Featured
I Don’t Have Time: Getting Over the Fear to Launch Your Podcast
jcasabona
32
2.1k
Templates, Plugins, & Blocks: Oh My! Creating the theme that thinks of everything
marktimemedia
30
2.2k
The Success of Rails: Ensuring Growth for the Next 100 Years
eileencodes
44
7k
A better future with KSS
kneath
238
17k
4 Signs Your Business is Dying
shpigford
182
22k
Fantastic passwords and where to find them - at NoRuKo
philnash
51
3k
Faster Mobile Websites
deanohume
306
31k
Distributed Sagas: A Protocol for Coordinating Microservices
caitiem20
330
21k
Being A Developer After 40
akosma
89
590k
What's in a price? How to price your products and services
michaelherold
244
12k
Fontdeck: Realign not Redesign
paulrobertlloyd
83
5.4k
Designing for humans not robots
tammielis
250
25k
Transcript
Scaling Science
[email protected]
Dr. Matt Wood
Hello
Science
Beautiful, unique.
Impossible to re-create
Snowflake Science
Reproducibility
Reproducibility scales science
Reproduce. Reuse. Remix.
Value++
None
How do we get from here to there? 5PRINCIPLES REPRODUCIBILITY
OF
1. Data has Gravity 5 PRINCIPLES REPRODUCIBILITY OF
Increasingly large data collections
1000 Genomes Project: 200Tb
Challenging to obtain and manage
Expensive to experiment
Large barrier to reproducibility
Data size will increase
Data integration will increase
Data dependencies will increase
Move data to the users
Move data to the users X
Move tools to the data
Place data where it can consumed by tools
Place tools where they can access data
None
None
None
Canonical source
None
More data, more users, more uses, more locations
Cost
Force multiplier
Cost
Complexity
Cost and complexity kill reproducibility
Utility computing
Availability
Pay-as-you-go
Flexibility
Performance
CPU + IO
Intel Xeon E5 NVIDIA Tesla GPUs
240 TFLOPS
90 - 120k IOPS on SSDs
Performance through productivity
Cost
On-demand access
Reserved capacity
100% Reserved capacity
100% Reserved capacity On-demand
100% Reserved capacity On-demand
Spot instances
Utility computing enhanced reproducibility
None
2. Ease of use is a pre-requisite 5 PRINCIPLES REPRODUCIBILITY
OF
http://headrush.typepad.com/creating_passionate_users/2005/10/getting_users_p.html
Help overcome the suck threshold
Easy to embrace and extend
Choose the right abstraction for the user
$ ec2-run-instances
$ starcluster start
None
Package and automate
Package and automate Amazon machine images, VM import
Package and automate Amazon machine images, VM import Deployment scripts,
CloudFormation, Chef, Puppet
Expert-as-a-service
None
None
1000 Genomes Cloud BioLinux
None
Your HiSeq data Illumina BaseSpace
Architectural freedom
Freedom of abstraction
3. Reuse is as important as reproduction 5 PRINCIPLES REPRODUCIBILITY
OF
Seven Deadly sins of Bioinformatics: http://www.slideshare.net/dullhunk/the-seven-deadly-sins-of-bioinformatics
Seven Deadly sins of Bioinformatics: http://www.slideshare.net/dullhunk/the-seven-deadly-sins-of-bioinformatics
Infonauts are hackers
They have their own way of working
The ‘Big Red Button’
Fire and forget reproduction is a good first step, but
limits longer term value.
Monolithic, one-stop-shop
Work well for intended purpose
Challenging to install, dependency heavy
Di cult to grok
Inflexible
Infonauts are hackers: embrace it.
Small things. Loosely coupled.
Easier to grok
Easier to reuse
Easier to integrate
Lower barrier to entry
Scale out
Build for reuse. Be remix friendly. Maximize value.
4. Build for collaboration 5 PRINCIPLES REPRODUCIBILITY OF
Workflows are memes
Reproduction is just the first step
Bill of materials: code, data, configuration, infrastructure
Full definition for reproduction
Utility computing provides a playground for bioinformatics
Code + AMI + custom datasets + public datasets +
databases + compute + result data
Code + AMI + custom datasets + public datasets +
databases + compute + result data
Code + AMI + custom datasets + public datasets +
databases + compute + result data
Code + AMI + custom datasets + public datasets +
databases + compute + result data
Package, automate, contribute.
Utility platform provides scale for production runs
Drug discovery on 50k cores: Less than $1000
5. Provenance is a first class object 5 PRINCIPLES REPRODUCIBILITY
OF
Versioning becomes really important
Especially in an active community
Doubly so with loosely coupled tools
Provenance metadata is a first class entity
Distributed provenance
1. Data has gravity 2. Ease of use is a
pre-requisite 3. Reuse is as important as reproduction 4. Build for collaboration 5. Provenance is a first class object 5PRINCIPLES REPRODUCIBILITY OF
None
Thank you aws.amazon.com @mza
[email protected]