By bloid
via erlangatwork.com
Published: Sep 01 2008 / 10:15
Our Erlang gateways were developed and deployed in phases starting with AIM/ICQ, GTalk, Yahoo, and finally MSN. Aside from minor protocol implementation bugs there were no problems and we were very satisfied with stability and performance. However, not long after releasing the MSN gateway we noticed that it used a ton of memory, and also periodically suffered massive spikes in memory use which invoked the Linux kernel's OOM killer. This lead to a crash course in debugging running Erlang apps, and a great appreciation for the years of real-world lessons that have influenced the features and design of Erlang/OTP.
-
3 Breakthrough Ways to Visualize HTML5 Audio
-
ICEFaces 3.0 Released
-
The Curious Story of the Smart Microsoft Developer Who Couldn’t Find a Job (he liked)
-
Responsive Images: How they Almost Worked and What We Need
-
The Basics of Wireless Roaming Latency Analysis
-
NoSQL Adoption Is on the Rise, a New Survey Suggests
Add your comment
