For users who aggregate data from around the web, you’ll find our latest core to be an integral part of your toolbox. s1 cores are comparable in performance to c1 cores with one extra trick up their sleeve: each job running in parallel will have a different IP.
Why is this important?
Using unique IPs is necessary to minimize the automated throttling most sites will impose when seeing fast, repeated access from a single IP.
How do I use it?
If you’re already using our c1 cores, all you’ll need to do is set the _type keyword.
cloud.call(func, _type=’s1′)
How much?
$0.04/core/hour
Why don’t other cores have individual IPs?
For other core types, such as c2, multiple cores may be running on a single machine that is assigned only a single IP address. When using s1 cores, you’re guaranteed that each core sits on a different machine.
Suggestions?
We’re excited to move the s1 core type out of beta for our customers. If you have any suggestions for other core types you would like to see, please let us know.
Tags: core types, new features, s1, scraping
Categories: What's New
You can follow any responses to this entry through the RSS 2.0 feed.
[...] adopters were in fact web companies who aggregate content from all over the web. In fact, the s1 (scraping) core was in direct response to the needs of this class of [...]