Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
lil_tee
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
10 ms
·
61.
▲
What Real-Time Gambling Data Reveals About Sports: Introducing Gambletron 2000
(news.rapgenius.com)
13 points
by
lil_tee
13y ago
|
0 comments
62.
▲
One Weird Trick to Make PostgreSQL 15,000x Faster
(news.rapgenius.com)
3 points
by
lil_tee
13y ago
|
0 comments
63.
▲
Seattle vs Denver Live Win Probability – Gambletron 2000
(gambletron2000.com)
2 points
by
lil_tee
13y ago
|
0 comments
64.
▲
What do Rappers Have in Common with New York Times Wedded Couples?
(news.rapgenius.com)
11 points
by
lil_tee
13y ago
|
2 comments
65.
▲
by
lil_tee
13y ago
I think the projection becomes relevant when you're looking at "straight" borders like Colorado. A great circle will bend slightly north of the northern border, so you can actually just barely touch Wyoming and Nebraska, but
66.
▲
What's the Most Concave State in the U.S.? Using R to Solve a Geography Puzzle
(news.rapgenius.com)
177 points
by
lil_tee
13y ago
|
57 comments
67.
▲
N-gram Analysis of the New York Times Weddings Section
(news.rapgenius.com)
250 points
by
lil_tee
13y ago
|
64 comments
68.
▲
Better Queuing Metrics With Updated New Relic Add-On
(blog.heroku.com)
8 points
by
lil_tee
14y ago
|
0 comments
69.
▲
by
lil_tee
14y ago
We have updated our post to incorporate some popular suggestions and reactions into our simulations: http://rapgenius.com/1504221
70.
▲
by
lil_tee
14y ago
Simulation author here with some additional analysis using a faster distribution of request times. If you use a distribution with median 50 ms, 90th percentile 225 ms, and 99.9th percentile 898 ms, then you need 30 intelligent dynos to hand
71.
▲
by
lil_tee
14y ago
I'm not familiar with minimum-of-two-random routing, but it does seem like assigning request to dynos in sequence would perform much better than assigning randomly (ie in a scenario with n dyno capacity, request 1 => dyno 1, request 2 =
72.
▲
by
lil_tee
14y ago
But you never want to have a queue on any of your dynos! A queued request means that a user is waiting with no response. If your goal is to have 0 (or less than epsilon) requests queued, it takes far fewer dynos if the requests are routed