For our purposes Common Crawl's corpus was missing too many websites (possibly due to robots.txt configs of websites) Also we needed some deep coverage which CC could not provide.
We tried a bunch of technologies like Nutch, Heritrix, Storm Crawler, ... eventually settled on Mixnode and since it's a 'cloud platform' we didn't really have to change anything.
19 comments
[ 7.2 ms ] story [ 52.7 ms ] threadAs one would expect the vast majority of data recorded is text/* (html,...)
Will update this in a few days with more data.
The data does not follow a DFS or BFS pattern so pages/site varies greatly by a host's server capacity and anti-crawling configs.
There was a minimum of 10 seconds between followup requests to the same website unless robots.txt had a lower delay. Pretty polite...
As for processing the data we crawled, we are using ArchiveSpark (https://github.com/helgeho/ArchiveSpark)
Also, Mixnode defaults on Amazon S3 for storage which was ok with us since we're using EC2 for processing the results.