Scribd
Upload
113 views

Awesome Big Data Algorithms

The document provides an overview of algorithms for analyzing large datasets, known as "big data algorithms". It discusses using probabilistic and approximate algorithms when exact solutions are not feasible due to the large scale of the data. Specific algorithms covered include skip lists, HyperLogLog counting, Bloom filters, and CountMin sketches. The document also discusses applications of these types of algorithms to problems in biology like reconstructing genomes from shotgun sequencing data.

Uploaded by

Yamabushi
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
113 views

Awesome Big Data Algorithms

The document provides an overview of algorithms for analyzing large datasets, known as "big data algorithms". It discusses using probabilistic and approximate algorithms when exact solutions are not feasible due to the large scale of the data. Specific algorithms covered include skip lists, HyperLogLog counting, Bloom filters, and CountMin sketches. The document also discusses applications of these types of algorithms to problems in biology like reconstructing genomes from shotgun sequencing data.

Uploaded by

Yamabushi
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 37

Awesome

Big Data Algorithms

http://xkcd.com/1185/

Awesome Big Data Algorithms


C. Titus Brown [email protected] Asst Professor, Michigan State University (Microbiology, Computer Science, and BEACON)

Welcome!
More of a computational scientist than a computer scientist; will be using simulations to demo & explore algorithm behavior.

Send me questions/comments @ctitusbrown, or [email protected].

Features
I will be using Python rather than C++, because Python is easier to read.

I will be using IPython Notebook to demo.

I apologize in advance for not covering your favorite data structure or algorithm.

Outline
The basic idea Three examples
Skip lists (a fast key/value store) HyperLogLog Counting (counting discrete elements) Bloom lters and CountMin Sketches

Folding, spindling, and mutilating DNA sequence References and further reading

The basic idea


Problem: you have a lot of data to count, track, or otherwise analyze. This data is Data of Unusual Size, i.e. you cant just brute force the analysis. For example,
Count the approximate number of distinct elements in a very large (innite?) data set Optimize queries by using an ecient but approximate prelter Determine the frequency distribution of distinct elements in a very large data set.

Online and streaming vs. oine


Large is hard; innite is much easier. Oine algorithms analyze an entire data set all at once. Online algorithms analyze data serially, one piece at a time. Streaming algorithms are online algorithms that can be used for very memory & compute limited analysis.

Exact vs random or probabilistic


Often an approximate answer is sucient, esp if you can place bounds on how wrong the approximation is likely to be. Often random algorithms or probabilistic data structures can be found with good typical behavior but bad worst case behavior.

For one (stupid) example


You can trim 8 bits o of integers for the purpose of averaging them

Skip lists
A randomly indexed improvement on linked lists. Each node can belong to one or more vertical levels, which allow fast search/insertion/deletion ~O(log(n)) typically!

wikipedia

Skip lists
A randomly indexed improvement on linked lists. Very easy to implement; asymptotically good behavior.

From reddit, if someone held a gun to my head and asked me to implement an ecient set/map storage, I would implement a skip list. (Response: does this happen to you a lot??)

wikipedia

Channel randomness!
If you can construct or rely on randomness, then you can easily get good typical behavior.

Note, a good hash function is essentially the same as a good random number generator

HyperLogLog cardinality counting


Suppose you have an incoming stream of many, many objects. And you want to track how many distinct items there are, and you want to accumulate the count of distinct objects over time.

Relevant digression:
Flip some unknown number of coins. Q: what is something simple to track that will tell you roughly how many coins youve ipped? A: longest run of HEADs. Long runs are very rare and are correlated with how many coins youve ipped.

Cardinality counting with HyperLogLog


Essentially, use longest run of 0-bits observed in a hash value. Use multiple hash functions so that you can take the average. Take harmonic mean + low/high sampling adjustment => result.

Bloom lters
A set membership data structure that is probabilistic but only yields false positives. Trivial to implement; hash function is main cost; extremely memory ecient.

My research applications
Biology is fast becoming a data-driven science.

http://www.genome.gov/sequencingcosts/

feeding books into a paper shredder, digitizing the shreds, and reconstructing the book.

Shotgun sequencing analogy:

Although for books, we often know the language and not just the alphabet J

Shotgun sequencing is --

Randomly ordered. Randomly sampled. Too big to eciently do multiple passes

Shotgun sequencing
Genome (unknown) X X X X X X X X X X X X X X X X Reads (randomly chosen; have errors) X

Coverage is simply the average number of reads that overlap each true base in genome. Here, the coverage is ~10 just draw a line straight down from the top through all of the reads.

Random sampling => deep sampling needed

Typically 10-100x needed for robust recovery (300 Gbp for human)

Random sampling => deep sampling needed

Typically 10-100x needed for robust recovery (300 Gbp for human) But this data is massively redundant!! Only need 5x systematic! All the stu above the red line is unnecessary!

Streaming algorithm to do so: digital normalization


True sequence (unknown) Reads (randomly sequenced)

Digital normalization
True sequence (unknown) X Reads (randomly sequenced)

Digital normalization
True sequence (unknown) X X X Reads (randomly sequenced) X X X X X X X

Digital normalization
True sequence (unknown) X X X Reads (randomly sequenced) X X X X X X X

Digital normalization
True sequence (unknown) X X X Reads (randomly sequenced) X X X X X X X

X If next read is from a high coverage region - discard

Digital normalization
True sequence (unknown) X X X X Reads (randomly sequenced) X X X X X X X X

X X X X X X X X X X

X X

Redundant reads (not needed for assembly)

Storing data this way is better than best- possible information-theoretic storage.

Pell et al., PNAS 2012

Use Bloom lter to store graphs


Graphs only gain nodes because of Bloom lter false positives.

Pell et al., PNAS 2012

Some assembly details


This was completely intractable. Implemented in C++ and Python; good practice (?) Weve changed scaling behavior from data to information. Practical scaling for ~soil metagenomics is 10x:
need < 1 TB of RAM for ~2 TB of data, ~2 weeks. Before, ~10TB.

Smaller problems are pretty much solved. Just beginning to explore threading, multicore, etc. (BIG DATA grant proposal) Goal is to scale to 50 Tbp of data (~5-50 TB RAM currently)

Concluding thoughts
Channel randomness. Embrace streaming. Live with minor uncertainty. Dont be afraid to discard data. (Also, Im an open source hacker who can confer PhDs, in exchange for long years of low pay living in Michigan. E-mail me! And dont talk to Brett Cannon about PhDs rst.)

References
SkipLists: Wikipedia, and John Shipmans code:
http://infohost.nmt.edu/tcc/help/lang/python/examples/pyskip/pyskip.pdf

HyperLogLog: Aggregate Knowledges blog,


http://blog.aggregateknowledge.com/2012/10/25/sketch-of-the-day-hyperloglog-cornerstone-of-a-big-data-infrastructure/

And: https://github.com/svpcom/hyperloglog

Bloom Filters: Wikipedia


Our work: http://ivory.idyll.org/blog/ and http://ged.msu.edu/interests.html [email protected]

You might also like