<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: FaceStat scales!</title>
	<link>http://blog.doloreslabs.com/2008/06/facestat-scales/</link>
	<description></description>
	<pubDate>Fri, 21 Nov 2008 12:22:18 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: ilaçlama Hizmetleri</title>
		<link>http://blog.doloreslabs.com/2008/06/facestat-scales/#comment-628</link>
		<dc:creator>ilaçlama Hizmetleri</dc:creator>
		<pubDate>Sun, 02 Nov 2008 10:28:56 +0000</pubDate>
		<guid>http://blog.doloreslabs.com/2008/06/facestat-scales/#comment-628</guid>
		<description>thanks YOu</description>
		<content:encoded><![CDATA[<p>thanks YOu</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Hutchison</title>
		<link>http://blog.doloreslabs.com/2008/06/facestat-scales/#comment-406</link>
		<dc:creator>Brian Hutchison</dc:creator>
		<pubDate>Wed, 30 Jul 2008 17:12:31 +0000</pubDate>
		<guid>http://blog.doloreslabs.com/2008/06/facestat-scales/#comment-406</guid>
		<description>Answering my above question, I found info on output_buffers here:
http://www.ruby-forum.com/topic/152021#new</description>
		<content:encoded><![CDATA[<p>Answering my above question, I found info on output_buffers here:<br />
<a href="http://www.ruby-forum.com/topic/152021#new" rel="nofollow">http://www.ruby-forum.com/topic/152021#new</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Hutchison</title>
		<link>http://blog.doloreslabs.com/2008/06/facestat-scales/#comment-405</link>
		<dc:creator>Brian Hutchison</dc:creator>
		<pubDate>Wed, 30 Jul 2008 16:56:10 +0000</pubDate>
		<guid>http://blog.doloreslabs.com/2008/06/facestat-scales/#comment-405</guid>
		<description>Hello, we're going live with a nginx fronted site and I'd like to know how you increased your open file handling limits. Did you just change worker_rlimit_nofile?  Did you change any other parts of your conf?  If you have any thoughts to share on output_buffers &#38; postpone_output, I'd love to hear about those too! :)

Great post.</description>
		<content:encoded><![CDATA[<p>Hello, we&#8217;re going live with a nginx fronted site and I&#8217;d like to know how you increased your open file handling limits. Did you just change worker_rlimit_nofile?  Did you change any other parts of your conf?  If you have any thoughts to share on output_buffers &amp; postpone_output, I&#8217;d love to hear about those too! :)</p>
<p>Great post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephan Schmidt</title>
		<link>http://blog.doloreslabs.com/2008/06/facestat-scales/#comment-384</link>
		<dc:creator>Stephan Schmidt</dc:creator>
		<pubDate>Mon, 21 Jul 2008 16:41:30 +0000</pubDate>
		<guid>http://blog.doloreslabs.com/2008/06/facestat-scales/#comment-384</guid>
		<description>“I enjoy writing Java more than writing Ruby” should be considered potentially harmful and dangerous.

I enjoy writing Java more than writing Ruby. So consider me dangerous!

"@brandon no one codes in java because they want to."

I do!

Peace
-stephan</description>
		<content:encoded><![CDATA[<p>“I enjoy writing Java more than writing Ruby” should be considered potentially harmful and dangerous.</p>
<p>I enjoy writing Java more than writing Ruby. So consider me dangerous!</p>
<p>&#8220;@brandon no one codes in java because they want to.&#8221;</p>
<p>I do!</p>
<p>Peace<br />
-stephan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dude</title>
		<link>http://blog.doloreslabs.com/2008/06/facestat-scales/#comment-359</link>
		<dc:creator>Dude</dc:creator>
		<pubDate>Mon, 14 Jul 2008 04:00:41 +0000</pubDate>
		<guid>http://blog.doloreslabs.com/2008/06/facestat-scales/#comment-359</guid>
		<description>Brandon, why do you have to be such a dick ?
Ruby != Groovy... understandable... but... 

Ruby is an extremely beautiful language, tons of users, awesome community, with a bunch of love from Sun (ala JRuby, etc).

Yeah, there are a lot of fan boys in every language... and you could say especially people coming from... say... PHP to Rails, many of those who don't know anything about OOP, and still rave about how awesome it is without knowing anything about it.

Alas... many come from Java to Ruby, for good reasons.  So, don't be such a prick.</description>
		<content:encoded><![CDATA[<p>Brandon, why do you have to be such a dick ?<br />
Ruby != Groovy&#8230; understandable&#8230; but&#8230; </p>
<p>Ruby is an extremely beautiful language, tons of users, awesome community, with a bunch of love from Sun (ala JRuby, etc).</p>
<p>Yeah, there are a lot of fan boys in every language&#8230; and you could say especially people coming from&#8230; say&#8230; PHP to Rails, many of those who don&#8217;t know anything about OOP, and still rave about how awesome it is without knowing anything about it.</p>
<p>Alas&#8230; many come from Java to Ruby, for good reasons.  So, don&#8217;t be such a prick.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brandon Franklin</title>
		<link>http://blog.doloreslabs.com/2008/06/facestat-scales/#comment-341</link>
		<dc:creator>Brandon Franklin</dc:creator>
		<pubDate>Sat, 21 Jun 2008 22:00:31 +0000</pubDate>
		<guid>http://blog.doloreslabs.com/2008/06/facestat-scales/#comment-341</guid>
		<description>Ohhh I get it, I guess the Ruby people don't understand that "running on a JVM" doesn't mean "coding in Java".  Might wanna do a little research first, peeps.  See:  JRuby, Jython, and Groovy.</description>
		<content:encoded><![CDATA[<p>Ohhh I get it, I guess the Ruby people don&#8217;t understand that &#8220;running on a JVM&#8221; doesn&#8217;t mean &#8220;coding in Java&#8221;.  Might wanna do a little research first, peeps.  See:  JRuby, Jython, and Groovy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brandon Franklin</title>
		<link>http://blog.doloreslabs.com/2008/06/facestat-scales/#comment-340</link>
		<dc:creator>Brandon Franklin</dc:creator>
		<pubDate>Sat, 21 Jun 2008 21:58:03 +0000</pubDate>
		<guid>http://blog.doloreslabs.com/2008/06/facestat-scales/#comment-340</guid>
		<description>LOL I'd like to see anybody code the medical imaging client/server application I work on in Ruby instead of Java and get it to perform at all!

Besides I'm not talking about Java vs. Ruby.  I'm talking about Grails vs. Ruby on Rails.  Groovy != Java.

As far as I can tell, Grails is more beautiful and elegant than RoR.

It is amusing to see Ruby fanbois on the attack though.  I'll admit I've never seen that before.</description>
		<content:encoded><![CDATA[<p>LOL I&#8217;d like to see anybody code the medical imaging client/server application I work on in Ruby instead of Java and get it to perform at all!</p>
<p>Besides I&#8217;m not talking about Java vs. Ruby.  I&#8217;m talking about Grails vs. Ruby on Rails.  Groovy != Java.</p>
<p>As far as I can tell, Grails is more beautiful and elegant than RoR.</p>
<p>It is amusing to see Ruby fanbois on the attack though.  I&#8217;ll admit I&#8217;ve never seen that before.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Higginbotham</title>
		<link>http://blog.doloreslabs.com/2008/06/facestat-scales/#comment-329</link>
		<dc:creator>James Higginbotham</dc:creator>
		<pubDate>Tue, 17 Jun 2008 01:54:13 +0000</pubDate>
		<guid>http://blog.doloreslabs.com/2008/06/facestat-scales/#comment-329</guid>
		<description>Brendan,

I was just curious how you found Slicehost to work in this situation and if Slicehost had a different solution that they weren't announcing publicly for situations like yours. 

I have personally steered away from the round robin DNS approach in the past. If one of your frontline servers is down, it can take a little time to propagate DNS updates to remove the server from the round-robin. Some DNS servers will cache the old IP for a period of time, thereby preventing access to your app until their cache is flushed or until the slice is operational once again. RR DNS is not the best solution, but the best one with Slicehost and it gets the job done in a pinch. A reverse proxy would be optimal to prevent this as you mentioned. 

NAT is the one feature I'd love to see Slicehost add, as it would allow larger customers to add new slices behind their single public IP without depending upon a single slice to do the reverse proxy work or stale DNS situations when using RR DNS. I noticed that Amazon EC2 now has this, though I haven't investigated it fully.</description>
		<content:encoded><![CDATA[<p>Brendan,</p>
<p>I was just curious how you found Slicehost to work in this situation and if Slicehost had a different solution that they weren&#8217;t announcing publicly for situations like yours. </p>
<p>I have personally steered away from the round robin DNS approach in the past. If one of your frontline servers is down, it can take a little time to propagate DNS updates to remove the server from the round-robin. Some DNS servers will cache the old IP for a period of time, thereby preventing access to your app until their cache is flushed or until the slice is operational once again. RR DNS is not the best solution, but the best one with Slicehost and it gets the job done in a pinch. A reverse proxy would be optimal to prevent this as you mentioned. </p>
<p>NAT is the one feature I&#8217;d love to see Slicehost add, as it would allow larger customers to add new slices behind their single public IP without depending upon a single slice to do the reverse proxy work or stale DNS situations when using RR DNS. I noticed that Amazon EC2 now has this, though I haven&#8217;t investigated it fully.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: brendano</title>
		<link>http://blog.doloreslabs.com/2008/06/facestat-scales/#comment-328</link>
		<dc:creator>brendano</dc:creator>
		<pubDate>Tue, 17 Jun 2008 01:02:03 +0000</pubDate>
		<guid>http://blog.doloreslabs.com/2008/06/facestat-scales/#comment-328</guid>
		<description>James: that's right, we currently use round-robin between web server slices.  Every slice has its own public IP; I think I'm not understanding your concern.  We certainly could point our DNS records at a single slice and run a reverse proxy on there.

PJ, Chris: To be fair, Grails is in the Groovy language, not Java.  I rather liked Groovy the last time I used it; the biggest issue was that the compiler was hideously slow, though I'm sure it's faster now.  Probably F#/.NET is the most advanced dynamic language platform anyway :)</description>
		<content:encoded><![CDATA[<p>James: that&#8217;s right, we currently use round-robin between web server slices.  Every slice has its own public IP; I think I&#8217;m not understanding your concern.  We certainly could point our DNS records at a single slice and run a reverse proxy on there.</p>
<p>PJ, Chris: To be fair, Grails is in the Groovy language, not Java.  I rather liked Groovy the last time I used it; the biggest issue was that the compiler was hideously slow, though I&#8217;m sure it&#8217;s faster now.  Probably F#/.NET is the most advanced dynamic language platform anyway :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lukas</title>
		<link>http://blog.doloreslabs.com/2008/06/facestat-scales/#comment-327</link>
		<dc:creator>Lukas</dc:creator>
		<pubDate>Tue, 17 Jun 2008 00:51:15 +0000</pubDate>
		<guid>http://blog.doloreslabs.com/2008/06/facestat-scales/#comment-327</guid>
		<description>650k hits is actually what got through to Google analytics.  My best guess is that the actual traffic was 5-10 times higher.  Also the spikiness was a lot higher than reducing to 20hrs per day.  Our peak hourly load even without yhoo post is several times higher than average.</description>
		<content:encoded><![CDATA[<p>650k hits is actually what got through to Google analytics.  My best guess is that the actual traffic was 5-10 times higher.  Also the spikiness was a lot higher than reducing to 20hrs per day.  Our peak hourly load even without yhoo post is several times higher than average.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
