swrobel

19 ms·

1. 151.▲
   by swrobel 13y ago

   Exactly how I felt, great at small scale, but increasingly painful to use as you reach scale. By the way, great tool, thanks for building it!
2. 152.▲
   by swrobel 13y ago

   Good stuff schneems, in my case, too little, too late.
3. 153.▲
   by swrobel 13y ago

   Agree with both of you 100%, but the fact that Heroku forces this choice is a frustrating one nonetheless.
4. 154.▲
   by swrobel 13y ago

   That's a whole other conversation ;)
5. 155.▲
   by swrobel 13y ago

   I was using 2X dynos on Heroku. I did have memory issues and had to continually reduce the number of unicorns that I was running. I think CPU and disk were the major bottlenecks, but again, Heroku makes it hard to track down exactly what th
6. 156.▲
   by swrobel 13y ago

   Agree with most of what you say, but adding dynos increases concurrency but doesn't do anything to reduce response times. Sometimes you just need a faster box.
7. 157.▲
   by swrobel 13y ago

   Good to know! I've been meaning to look into Ansible & SaltStack, and you gave me the kick in the butt I needed. EDIT: ohai Andrew! Thanks for the comment.
8. 158.▲
   I left Heroku for OpsWorks and shaved 40% off response times(stefanwrobel.com)

   73 points by swrobel 13y ago|49 comments
9. 159.▲
   by swrobel 14y ago

   Anywhere to download MP3 or other audio-only versions to listen in the car?