Having to remeber what the boot2docker ip address sucks, wouldn't it be better to access it like localhost?
First you need to get the boot2docker ip address. You can get that in terminal:
$ boot2docker ip
On my computer I get:
|Description: 'Backup DynamoDB table to S3, convert export to Parquet, and add table to Athena'|
|Description: DynamoDB table name|
|Description: Percentage of table read throughput a backup can use. Expressed between 0.01 and 1.0. Defaults to 20% of available read throughput|
|# Run and fail|
|# AWS_ACCESS_KEY_ID=*** ruby connection_pool_issue.rb|
|# Does not crash|
|# empty_connection_pools_after_fork=true ruby connection_pool_issue.rb|
|# the Aws SDK maintains a ConnectionPool in Seahorse. After fork|
|# file descriptors are shared between the parent process and any child processes.|
|# Official docs are a _bit_ light on specifcs|
|# There are other options if you are interested in a general trace:|
|# * ruby -r tracer your_script.rb|
|# * https://ruby-doc.org/core-2.3.0/TracePoint.html|
|# What I'd like to be able to do is create a helper module / class that can be added to any class like so:|
Sometimes you need to iterate over a ton of items and you don't want the overhead of creating AR objects out of all of them. Hell, you only need a few things! Well, #pluck has your back.
But what if you want to iterate over many tonnes of items?
Pluck in batches to the rescue!
This isn't the exact code that I use in my code base, but it is damn close.