From: colmac@... Date: 2009-01-31T15:05:11+09:00 Subject: Re: Ruby on Solaris 10 performance problems On 2009-01-30 11:28:49 -0500, Colin Mackenzie said: > Thanks Peter and Robert for all your insights about his subject. This > whole thing came to light when I took one of our web based applications This illustrates the importance of complete disclosure of information and context. I had assumed this was a long running batch server. The fact that this is a web application tells us that response time rather than throughput is the variable of interest here. Before learning that this was a web application I had disagreed with Robert's view that the Intel PC was outperforming the Sun. > which is a Terminal management System and was going to port it to > Solaris system which happen to be a RISC platform. It was originally > written on a Ubuntu platform using an intel CPU and was going to be > ported to Red Hat Linux Enterprise on a Dell Blade system. Then > management changed and wanted it on Solaris. Long story there. When we > finally got it running it was discovered it took 5 seconds to load a > simple login page! It is a Ruby on Rails application and I found it was My opinion is that, in general, 100msec is reasonal build time target for web-ages. Five seconds to load a login page indicates that your application or infra has a real problem. That its less noticeabe on Intel doesn't mean you're home clear. The best way to dig into this sluggishness is with new relic. It is a superb production profiler > during a simple request to a controller to build a very simple page. The > process used arrays to do "certain" things during the process of > building the page. Hence, my simple ruby program to test. I simply cant > see any reason to re-architect the application so it will run on a RISC > platform. So in the end I am going to push for the original plan and put > this on a blade system of some type. Thanks again and yeah I am old > enough to remember those 50 floppies of Slackware except I was a > Yggdrasil fan :)