skysight-inc/HackerNews huggingface dataset:
Each connection forks a new process on the server, not a thread.
Israel is very multicultural; there are over 1.5 million Arab Muslim Israelis, and Israeli Jews include Americans, Europeans, Russians, Ethiopians, and various flavors of Arab/mizrachi Jew.
You mean you didn't read the Google Wallet terms of service? What kind of monster are you?
I can chime in here that I have had similar experiences at another large scale place :). Some requests would take a second or more to complete with the vast majority finishing in under 100MS. A solution was put in place that added about 5 MS to the average request, but also crushed the long tail(it just doesn't even exist anymore) and everything is hugely more stable and responsive.
I have restarted the petition to abolish the TSA here:

http://wh.gov/dUK1

or here:

https://petitions.whitehouse.gov/petition/abolish-tsa-favor-...
Shouldn't this be s/thread/process/ ?
Sure, but the real issue the article identifies is that, under random routing, they need to keep doubling the number of dynos to halve the odds of bad queueing, which leads to absurd factor of 50 requirements to get back to what they had before. With round robin, the increase should be much more linear.
There is a Quora question for this well, where more (helpful) comparison information might be posted in the future.

http://www.quora.com/Design/How-do-LayerVault-and-Pixelapse-...
No, trust me: I was on the original iPhone team and was responsible for Mobile Safari and "WebKit" on iOS, and you are pretty confused about the project.

For starters, "WebKit" is an overloaded term. There is "WebKit" the framework, which is a bridge between the actual gears (WebCore and JSCore) and applications. In other words, it is an API: an increasingly thin Obj-C layer on top of all the C++ that does the real work. Then there is the "WebKit Project", which is an umbrella term for all that stuff together (WebKit/WebCore/JSCore). Chrome for example neither uses WebKit proper if I recall correctly, nor the engine in JSCore (opting for v8 instead), and yet it is still considered a "WebKit browser". That's because what makes you "behave" like WebKit is WebCore, which actually handles DOM, rendering, CSS, etc etc. So saying that Apple releases WebKit for iOS is perfectly acceptable terminology, even if you are wanting to be pedantic about it. Now I don't know what you define as "juicy functionality", but I can assure you that WebCore is not just some helper library or something, WebCore more or less IS WebKit. It is certainly enough for you to be able to build your own custom browser for iOS. In fact, even if the iOS version was completely closed source, you could still take the desktop 100% open source WebKit and port it to the phone (just like Nokia and Google did for their phones).

So I guess I'm missing the relevancy of your point. If you just wanted to rant that Apple doesn't open source as much as it should, then I sympathize, but it really has nothing to do with the point I was making that due to the separate restrictive nature of the App Store policies, it doesn't matter if WebKit is or isn't open source because you aren't allowed to ship a custom browser engine anyways (at least not one that runs JavaScript).
Not only that, East Coast vs. West Coast at that...
I want this so bad. I once tried making an appointment for severe pain and was told three months and there was nothing sooner. They told me if I was in severe pain, I could visit my local ER, pay, and submit paperwork for reimbursement. I informed them that I could not afford that option and asked if they were going to treat me for alcoholism because I was going to drink myself to sleep every night for the next three months... I was then told, "Oh, how about next Tuesday. We have a number of reserved appointments that we can assign for high-need cases."

WHAT!?
Call It The iFob
Kirby CMS vs Stacey CMS: A quick comparison of flat-file PHP CMS
Just use the “Onload” demo option http://webdesign.maratz.com/lab/responsivetypography/onload/
Matadero de conejos
Does anyone know how if python applications are affected by this? I know they can handle multiple requests per dyno, I would be interested to know if random routing affects python apps too.
It is how Rails server behaves in itself, but that is also how Heroku tells you to do it.

Rails can be served with Unicorn ( http://unicorn.bogomips.org/ ) which is a forking app-server.

I do believe there was a trick a while back where you could get Heroku to run a Unicorn process on a dyno to get more requests out of it. The process is described here: http://blog.codeship.io/2012/05/06/Unicorn-on-Heroku.html
Pebble Watch Unboxing
The state of the union, in graphs
If they're being paid a fair salary according to the reality of their location, it's not a sweatshop. Attitudes like that keep developing countries in poverty by preventing them from taking advantage of the few upper hands they have over developed countries.
Paypal announces FIDO Alliance for passwordless authentication
http://stackoverflow.com/questions/6370479/heroku-cedar-slow... (from june 2011), the first discovery of cedar stack being slower than the bamboo stack
What's the advantage of randomized routing over intelligent routing? Why would this change be made?
I kind of saw this coming when they announced the Xi3 last month as being a Valve hardware platform. Originally when I saw Jeri Ellsworth hired, and some of the secrecy behind it, I felt they were trialing something out, because I sure didn't expect any sort of hardware to come out of it. If they found a small form-factor device already on the market, what good are the engineers they brought in to develop hardware for them?
OK, maybe I'm missing something here, but it seems to me that the OP's real problem is that he's artificially limiting himself to one request per dyno. They now allow a dyno to serve more than one request at a time, and he's presenting that as a bad thing! It seems to me that the answer to Rap Genius' problems is not "rage at Heroku," but rather "gem 'unicorn'".
> Wayne here. We're extremely proud of the work that the team here at Crashlytics has put into our crash reporting solution.

Can you explain why you're using headers for private data structures from the Mac SDK on iOS, while also stating the following?

"At Crashlytics, one of our founding principals has been an extreme (some would say, absurd) attention to detail. Crash detection and reporting, particularly on iOS, is a complex and esoteric problem to solve, with arcane restrictions that throw modern programming practices out the window."

Copying in private headers from the Mac SDK for use on iOS isn't something you can do accidentally.

> There are many flaws in PLCR that we've addressed -- our customers,like Twitter, Vine, Square, Yelp, OpenTable, Hipmunk, Delta, Kayak, and others, enjoy the increased visibility as well as the wider net to catch issues that other solutions cannot.

We're discussing systems software engineering on the level of compilers and operating systems. Without concrete information, you are not providing what an actual engineer requires to evaluate your solution.

This topic is deep, broad, and complicated. This deserves honest engineering discourse.

A specific example. In a blog post, you state:

"Need to allocate memory at crash-time? Revisit your approach. Thinking of calling an Objective-C method? Dream on."

Those things are not possible because of the requirement that signal and exception handlers be async-safe. Ironically, while Crashlytics does not use Objective-C, it still includes code that is not async-safe.

These kinds of mistakes are a fact of engineering, which is why good engineers are humble engineers. Your unequivocal boastful marketing -- and evaluation of other solutions -- is perhaps not entirely forthcoming.
Version Control is a concepts that every dicipline, that needs to manage documents, should try to implement.
100,000 lines. Wonder what it would take to crowd source a port? Best "modern" language? Java? Javascript? Go?
I'm inclined to wait until Heroku weighs in to render judgement. Specifically, because their argument depends on this premise:

> But elsewhere in their current docs, they make the same old statement loud and clear:
> The heroku.com stack only supports single threaded requests. Even if your applicaExplaintion were to fork and support handling multiple requests at once, the routing mesh will never serve more than a single request to a dyno at a time.

They pull this from Heroku's documentation on the Bamboo stack [1], but then extrapolate and say it also applies to Heroku's Cedar stack.

However, I don't believe this to be true. Recently, I wrote a brief tutorial on implementing Google Apps' openID into your Rails app.

The underlying problem with doing so on a free (single-dyno) Heroku app is that while your app makes an authentication request to Google, Google turns around and makes a "oh hey" request to your app. With a single-concurrency system, Google your app times out waiting for Google to get back to you and Google won't get back to you until your app gets back to you so hey deadlock.

However, there is a work-around on the Cedar stack: configure the unicorn server to supply 4 or so worker processes for your web server, and the Heroku routing mesh appropriately routes multiple concurrent requests to Unicorn/my app. This immediately fixed my deadlock problem. I have code and more details in a blog post I wrote recently. [2]

This seems to be confirmed by Heroku's documentation on dynos [3]:
> Multi-threaded or event-driven environments like Java, Unicorn, and Node.js can handle many concurrent requests. Load testing these applications is the only realistic way to determine request throughput.

I might be missing something really obvious here, but to summarize: their premise is that Heroku only supports single-threaded requests, which is true on the legacy Bamboo stack but I don't believe to be true on Cedar, which they consider their "canonical" stack and where I have been hosting Rails apps for quite a while.

[1] https://devcenter.heroku.com/articles/http-routing-bamboo

[2] http://www.thirdprestige.com/posts/your-website-and-email-ac...

[3] https://devcenter.heroku.com/articles/dynos#dynos-and-reques...

[edit: formatting]
I am sorry to hear of your situation...please don't take offense.

You say "I am not eager to search for a job...", yet you ask " Is there anybody willing to give me a job and be able to get me a work visa?" That does not make sense. It seems the best choice is to leave Iran. If you don't want a software job, freelance on Odesk or Elance. I'm sure you can find a job willing to give you a visa. Try Canada, many people I know there are on a work visa.
And just a follow-up. Malamud sees our conversation differently.

1. He does not like my characterization of our conversation. (It is hard to tell how much he doesn't like it, but I get the feeling he thinks it is extremely offensive.) But that is how I felt the conversation went. I try and convince him to put up text or even RTF versions, and I get back a response about legal analysis and legal representation. And that's how our conversation ended. This last conversation ended only slightly worse.

2. It appears he doesn't like my choice of language, or my form. Understandable, but all the words I have chosen are in the dictionary, and they are not in the dictionary because the Queen of England wanted them to be. They have function and purpose, and I believe their usage is valid to show extreme displeasure (towards a government institution and its directors) on an extremely important issue. This is how I feel, and I want others that feel the same way to know they are not alone. Hacker News can censor me, but I will not censor myself.

3. I'm not "grandstanding". I really don't care about recognition for my work. I doubt saying "fuck you" in a post is going to earn me much praise or impress anyone positively. My code sure won't. What I want is for anyone to be able to run (Geo)SPARQL queries against the law--damn the consequences. I would actually prefer to assign my copyright on my code to someone that can really put it to use. But I just don't see that happening anytime soon. (They were on the web for years under a CC0 license--no one cared.) I guess I could get a .org and make a snazy looking website and post it here and have no one care, but I would rather just put up a SPARQL endpoint and have no one care, or have someone else do it--like the government.

4. He published the CCR in 2008. But I must point out the same thing I have been trying to point out to him for years, and the subject of my post: HTML (or even RTF) is not the same thing as PDF scans. There is no Python library for that. I cannot derive RDF from them. I cannot search them in any robust way. For example, they will not show up in Google results. I think all these other issues are detracting from this: people should be able to grok the law. Easily. We can call China from anywhere in the world on the cheap, we can do all sorts of crazy things, but not grok the law.

That deserves a little vulgar language.
sudo for the user doing the deploy but not for the user running the app. The default is to run as the deploy user but you can change it.
Created an Unofficial Hacker News / YC Shirt For Everyone
Which spawned Apple's MPW IDE and their MacApp C++ framework, which ultimately gave way to Metrowerks CodeWarrior and the PowerPlant C++ framework. It's actually pretty amazing that for most of the 90s Apple let Metrowerks own the developer experience.

I always thought that Jobs' greatest triumph in pushing Rhapsody was bringing their developers back to using their own tools (though I suppose Carbon could be considered a short term loss).
If it's true, I can't see how random routing can be anything but a cynical cash grab.

Even a very simple algorithm like round robin would give you a significantly better latency characteristic wouldn't it?
Is it so that a dyno can only handle a single user request at a time?

Why dos it not use some kind of scheduling system to handle other task while one task is waiting on i/o?
The problem is the request arrival rate vs the distribution of service times in your app.

New Relic may be giving you an average number you feel happy about, but the 99th percentile numbers are extremely important. If you have a small fraction of requests that take much longer to process, you'll end up with queuing, even with a predictive least loaded balancing policy.

This is a very common performance problem in rails apps, because developers often use active record's associations without any sort of limit on row count, not considering that in the future individual users might have 10000 posts/friends/whatever associated object.

Fix this and you'll see your end user latency come back in line.
It's been tried before (Apture and a crowd-sourced proof-reading plug-in I can't remember the name of). It needs critical mass to work, but it might very well on a very community-focused platform.
Angular JS Resources
Because the whole point is that you shouldn't have to.
BTW, here's a counter-intuitive solution if using pgbouncer is not possible. Simply drop and reestablish connections on every request.

In theory this is horrible, since PG connections are so expensive. In practice the cost of establishing a connection is negligible for a Rails app.

I do suspect this will make performance "fall-off-the cliff" as you get close to capacity.
Master Java recursion - Starting with Fibonacci
Great Micro-Interactions Through Minimum Viable Features
I'm a white guy (as white as wonder bread and twinkies, only thing missing is the blond hair, and blue eyes) but with an very common first and last name and a Persian middle name.

For 5 years every time I flew, I was subjected to 'random' extra inspection, and was unable to check in online. When I questioned this, I was absolutely assured it was random, and there was nothing I could do about it. I don't plan on living the rest of my life in fear of the unknown, planes crash, people die, these things happen, its statistically less likely to die from terrorism then it is from a normal plane crash, consider that.

I feel your pain, and its absolutely not right, and I hope in my lifetime, we come to our senses or I fear it may eventually result in a revolution.
True, I agree with you that if they can credibly convince the remaining employees that this is a one-time event due to extraordinary circumstances, and they are sure (as much as anything can be sure) it is not going to be repeated for >=5 years, culture is recoverable.

I've never seen that happen before, but I also mostly have information about more bureaucratic companies (especially my dad working for a top-100 global conglomerate as I was growing up), so Valve might do it right. One reason to think they might is the lack of lots of layers of management: multiple layoff rounds are often due to trying to cut the least possible to fulfill a target, but using the most optimistic assumptions, so finding out a few months later that, surprise, it wasn't enough.

I also agree that one round is pretty much the max you can explain away. Once you've gone to two, nobody believes that this is the last one.
It seems you're almost the only one who understood this.
Also,

MBP: 2880x1800
Dell: 1920x1080
That's a much more scalable approach. Supercharging stations, etc, seem like an insufficient band-aid. Imagine a gas station with each pump occupied for 30 minutes a piece.
When Facebook did this it made them the evil empire. Why isn't the front page full of stories about how to ditch Google?
Couple, the Social App for Couples, Adds Snapchat Feature
This is how I run my apps as well, and they seem to handle more than one request concurrently per dyno, but I'm not smart enough to dispute this post, so I'm just sitting back and watching.
-Yeah, maybe have chemical sensing devices with air intakes at floor level to screen for bombs on shoes,

Good idea, that way you can f'up a few hundred peoples day by spilling a 'coke' on a busy path way.

And by coke I mean some benign chemical that is none the less detected as explosive precursor by the machines.
I seem to recall Google mentioning on some blog several years ago that high variance in response latency degrades user experience much more than slightly higher average request times. I can't find the link though; if anyone has it, I'd be grateful.
But will Israeli security practices scale? Ben Gurion served a bit over 13 million passengers in 2012. JFK served over 47 million.
> Indeed, you can end up with an indeterminate state.

No. I think that claim is hysterically funny considering that Go developers almost never check all FOUR states of Go's style of error handling.

The problem Go is solving here wouldn't even exist if they had designed/used a better language in the first place.

Maybe Go people should stop drinking so much Kool-aid, because they sound like all these Node.js-ninja-rock-star kids who think that they revolutionize asynchronous programming while they reinvent threads, badly.
Engine Yard is more like opinionated configuration management. It allocates and configures EC2 instances that you can log into like normal. The software stack is HAProxy, nginx, unicorn, etc, and customizable through the web interface and/or chef.
>Also, to be fair to airlines, they have immense labour costs.

yeah. I also think that it's a good example of how some things? you can skimp on, while other things? not so much. I mean, if the airlines show that you can eliminate (or charge extra for) in-flight meals without disturbing anyone too much. You can even pack 'em in tighter (though, some people will pay extra for a little room.) - but yeah, you've still gotta keep the planes in the air.

Another interesting bit is that I'm not sure that it'd be cheaper to maintain airplanes to a lower standard, even without the customer backlash.

That's the thing; sometimes, the cheaper part is just as good- (for example, I think going supermicro is just as good as going dell, assuming the person assembling uses ESD protection.) - but other things? non-ecc ram, for instance, in my unscientific opinion, usually ends up being more expensive in terms of downtime and technician hours than ecc ram.

Of course, airlines are also almost all unionized; The hosting market is almost the opposite. Generally more is expected for less pay in the hosting market than of the same technical roles in other sectors. Traditionally, this means that many people start in the hosting market, then move up (certainly in terms of pay) into a corporate networking or corporate sysadmin role.
But if won by an Afghani or Iraqi it could be a PR win.
For this specific issue round robin isn't really any different from random routing. Anything that stands a good chance of queueing a request while other machines sit idle is going to be a problem.

The only way that round robin would be arguably better than random routing is if your random selection is not evenly distributed.
But then again, those two links don't address the core of the problem:

Heroku is used by tons of people around the world. Some of them are paying good money for the service. Given the amount of scrutiny under which they operate, what is the incentive for them to turn an algorithm into a less effective one and still charge the same amount of money in a growing "cloud economy" where companies providing the same kind of service are a dime a dozen (AWS, Linode, Engine Yard, etc)?

How does that benefit their business if "calling their BS" is as easy as firing Apache Benchmark, collecting results, drawing a few charts and flat out "prove" that they're lying about the service they provide??

I mean, I doubt Heroku is that stupid, they know how their audience doesn't give them much room for mistakes. So as nice as the story sounds on paper, I'd really like another take on all this, either from other users of Heroku, independent dev ops, researchers, routing algorithms specialists or even Heroku themselves before we all too hastily jump to sensationalist conclusions.
New Zealand has one with China, and a bunch of other countries. We also have almost no other import barriers, grey market imports are legal and we can even easily import and register second hand cars, impossible in most countries.
Did they take this survey at a porn convention?
> If anything, verbs do nothing without a noun to do them, and nouns need verbs to do anything.

O Canada! It's raining.
The problem is that he is comfortable with Google receiving his information (name, address, email) but not third party developers selling through Google.

Developers on Google Play should not be merchants. Google should be more than a payment processor — especially if they are going to take 30% just like Apple does.

Apple handles this a hell of a lot better: as a developer you don't see anything about your customers (except how many there are per country) and you don't have to compute and collect sales tax yourself for every region you sell in, nor do you have to manually handle returns.

I hear the Amazon App Store does this a lot better than Google Play.
It's not exactly so, if you use a server that spawns child processes: http://michaelvanrooijen.com/articles/2011/06/01-more-concur... you can potentially handle 3-4 requests per dyno at a time. That doesn't fix the root problem, though.
The reputational damage is going to cost them plenty, if it's any consolation. The journalist nerds are tearing them apart.
There's no evidence that patting down passengers like Burton has made air travel any safer.

I'm going to play the devil's advocate here. How on earth do you actually prove prevention techniques?
Now this might just be my opinion, but considering many of the people I know in the technology field have a disposable income of around $1k/month, I don't think there's very many people that would throw away 20% of it on an image dump. If you make more than that, then you are rich by my standards.