tyler

5 ms·

1.
by tyler 14y ago
95% of requests. But yeah! And thank you. :)
2.
by tyler 14y ago
TTFB at the 50th hovers around 175 microseconds, 75th is at 250 microseconds, 95th around 450 microseconds. As for the purging stuff, I do mean cross-region. So, it depends upon which node receives your purge request. 150ms is average, but
3.
by tyler 14y ago
We like to think that the exact number of requests is less important than exactly how they're handled. While it would be cool to go "we serve a billion requests a second", we're still an early stage startup. We're spending more time making
4.
by tyler 14y ago
I'm sorry that my statement is bothering you. I'm going based on numerous conversations with people considering using Fastly. It's quite possible that I have a skewed sample, however I'm not intentionally spreading FUD, for what that's wort
5.
by tyler 14y ago
Alright. Let's go point-by-point. The primary feature advertised on fastly's website is a feature every real CDN (as in, "not CloudFront") offers: an API to immediately purge your content. Every CDN offers a mechanism to purge content, bu
6.
by tyler 14y ago
Actually, tests from us and several of our customers have shown us significantly faster than Edgecast throughout the US and Europe. (I work at Fastly.)
7.
by tyler 14y ago
If that's what you're after you might want to check out Fastly. We're a CDN entirely based on Varnish, with all the features that implies.
8.
by tyler 15y ago
Fastly (fastly.com) is designed for exactly this purpose.
9.
by tyler 15y ago
Cmd + `
10.
by tyler 15y ago
No. Memcached on a reasonable server will do millions of requests per second. 50,000 updates per second is nothing for any modern cache. Also, replication has nothing to do with whether or not "without a cache" is a meaningful statement. Th
11.
by tyler 15y ago
"with no cache" is a bit of a misleading statement, considering the entirety of their data set is stored in RAM. Turns out you don't really need memcached if you don't read anything from disk.
12.
by tyler 15y ago
I had a little project a while ago that compiled Mustache templates into C. Never was completely done, but it mostly works: https://github.com/tyler/speed_stache
13.
Parse Releases Their REST API(parse.com)
76 points by tyler 15y ago|32 comments
14.
by tyler 15y ago
Greplin has to do huge scale information retrieval. This probably counts as engineering. (See: SIGIR)
15.
by tyler 15y ago
I don't mean to be pedantic, but the word "transparent", in this context, means "easily perceived or detected". I believe you're using it to mean the opposite.
16.
by tyler 15y ago
So, what the "thread-safe mode" does is enable threads in Rails. (i.e. one thread per request.) To my knowledge, it does not switch out thread-unsafe code for thread-safe code. Moreover, it's irrelevant. As I mentioned, this is unrelated to
17.
by tyler 15y ago
"Since Rails is not threadsafe, typically several processes will run in parallel on a machine, behind a threaded Web server such as Apache or nginx." This is incorrect. Rails 3 (and 2.3) are thread-safe. They typically run in multiple proce
18.
The Problem with Papers from Industry(blog.codalism.com)
2 points by tyler 16y ago|0 comments
19.
by tyler 16y ago
It sounds like you're conflating two techniques here. The first (as others have mentioned) is cosine similarity, which measures the angle between the vectors. However, the bit about 0s and 1s sounds like you're talking about locality-sensit
20.
by tyler 16y ago
Two useful implementations that this article misses are Array-compacted tries (aka dual-array tries) and Array-mapped tries. ACTs are nice due to the small memory footprint and good cache-locality, but have the downside of being difficult
21.
by tyler 16y ago
The actual blog post: http://conversations.nokia.com/2010/06/28/how-do-you-hold-yo...
22.
by tyler 16y ago
I think that rather than a simple "I will ignore X", his point was more "I will ignore X because experimental evidence indicates X is not true". This seems completely legitimate to me.
23.
by tyler 16y ago
This article is poorly written and flat out wrong. His second example simply shows a public post of his on a public group. His statement "Facebook makes public EVERYTHING about its users via its search API" is just incorrect. But of co
24.
by tyler 16y ago
That was very carefully crafted in order to not answer the question at all. Nicely done.
25.
by tyler 16y ago
You say "any changes would have to be carefully considered". So, are said changes being considered or are they not?
26.
by tyler 16y ago
That's an understatement.
27.
by tyler 16y ago
So, it turns out that the version of Mobile Safari on the iPhone doesn't support getBoundingClientRect, which we were relying on. The fix for that should go out soon, at which point it will work on your iPhone.
28.
by tyler 16y ago
All of them. :)
29.
by tyler 16y ago
Not that I'd actually recommend doing it, but I'd bet that technique does work some small percentage of the time. What does Facebook have to lose by seeming desperate at that stage? I think it's smart.
30.
by tyler 16y ago
We've talked about doing both of those things. They're high on my to-do list.

More ›