gpapilion

37 ms·

391.
Trouble Tickets: Annoying, but Useful(blog.hypergeometric.com)
2 points by gpapilion 15y ago|0 comments
392.
Two Quick Chef Gotchas(blog.hypergeometric.com)
2 points by gpapilion 15y ago|0 comments
393.
by gpapilion 15y ago
Sed and awk are two underused unix tools. One you learn how to use them well, you'll constantly surprise yourself with what one can do in a simple shell script.
394.
by gpapilion 15y ago
I always take issue with people talking about replication as a solution to scalability. It better to think of replication as a solution for availability.
395.
Physical Infrastructure for the Win(blog.hypergeometric.com)
1 points by gpapilion 15y ago|0 comments
396.
by gpapilion 15y ago
Did you pull this from my google+ post?
397.
Introduction to configuration management(sysadvent.blogspot.com)
1 points by gpapilion 15y ago|0 comments
398.
by gpapilion 15y ago
When I did a comparison of co-located vs. managed vs. cloud my numbers broken down as such: co-lo: 1x cost managed: 1.5-2x cost cloud: 2.25-4x cost This was with headcount changes figured into the pricing. (We did not see a head count reduc
399.
by gpapilion 15y ago
Amazon has only recently begun rendering pages via EC2 based images. But, yes, Amazon is not primarily hosted in its cloud.
400.
by gpapilion 15y ago
1. I understand that, and have heard that from you guys several times. The issue is the deserialization from JSON. The monkey patch solution I've see so far stores less data, essentially white listing the attributes for search. It sort of d
401.
by gpapilion 15y ago
I have three fundamental issues with Chef; 1. The node object ends up being two large, which leads to memory issues when a search returns more that 200 nodes (800MB of memory). 2. Chef discourages declarative configuration. 3. Chef lacks a
402.
by gpapilion 16y ago
The points are probably applicable to most scaling discussions, and not particular to python. I'm surprised there isn't any discussion of using a CDN. Its easy to eliminate static load, and it reduces latencies considerably. I do wish he we
403.
by gpapilion 16y ago
I actually doubt this merger will go through. This would put AT&T far ahead of Verizon in term of subscribers, even if they are less desirable due to the low ARPU. There isn't enough churn in the wireless market to balance the AT&T
404.
by gpapilion 16y ago
If you understand the limitations of the various products you can build a VERY reliable service. The reddit assumption of a single datacenter and single technology to store that data was an engineering failure. They essentially didn't have
405.
by gpapilion 16y ago
MySQL does not fare any better on a single EBS volume. The issues with EBS are systematic. Similarly you have to raid several volumes together to see decent performance, and this is the recommended AWS solution.
406.
by gpapilion 16y ago
>This example is a bit larger than the sh script, but it is >certainly more readable. I tend to disagree with the author on this point.