• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

Ruby on Rails

Collapse
X
  •  
  • Filter
  • Time
  • Show
Clear All
new posts

    #11
    All I can think of is that joke on another thread.

    - Knock knock!

    - Who's there?

    - <long pause> Java

    Comment


      #12
      Fill your boots with benchmarks..

      http://shootout.alioth.debian.org/

      PHP is putting in times 100* slower than java (-server JVM) , ruby is even worse, java is about 3 times slower than GNU C which is close to as fast as you can get.

      No doubts java was slow 10 years ago but it's about as fast as you can get now and I do not see anyone funding much research into PHP and RUBY performance like IBM and SUN were able to.

      Comment


        #13
        Originally posted by minestrone View Post
        No doubts java was slow 10 years ago but it's about as fast as you can get now and I do not see anyone funding much research into PHP and RUBY performance like IBM and SUN were able to.
        I recall that Microsoft are working closely with Zend to improve the performance of PHP, albeit specifically on M$ platforms.
        Where are we going? And what’s with this hand basket?

        Comment


          #14
          I have done a bit of PHP development but could not actually say much about what's under the hood. When you change a PHP page does it actually get compiled into memory and translated into something more than the actual text in the script?

          Looking at those benchmarks again it seems that ruby is the only one slower and also has more memory usage than java which is something I have noticed using it.

          Comment


            #15
            Originally posted by minestrone View Post
            I have done a bit of PHP development but could not actually say much about what's under the hood. When you change a PHP page does it actually get compiled into memory and translated into something more than the actual text in the script?

            Looking at those benchmarks again it seems that ruby is the only one slower and also has more memory usage than java which is something I have noticed using it.
            My (limited) understanding is that at a basic level PHP code is compiled at runtime when each page is requested, but various accelerators are available that offer the ability to cache the code in a compiled state.
            Where are we going? And what’s with this hand basket?

            Comment


              #16
              Originally posted by lightng View Post
              All I can think of is that joke on another thread.

              - Knock knock!

              - Who's there?

              - <long pause> Java
              It was actually me who posted that!

              Comment


                #17
                Originally posted by jkoder View Post
                It was actually me who posted that!
                Oh OK. Haha.

                Comment


                  #18
                  Originally posted by bogeyman View Post
                  Java was always 'the future' but never quite got there. It's still 'as slow as molasses in winter' even today.
                  Well that depends, as someone else said, you can write slow ram eating code in any language.

                  a common mistake is to forget to run the live system with '-server' on the JVM!

                  I know lots of enterprise systems running in java - these are scaleable systems processing thousands of transactions a minute.

                  One thing that is bad though is building web forms - this is a slow development task even with struts or whatever the latest fad is, in this respect PHP is much more productive and this needs to be balanced against the speed of the resulting system, it may be cheaper to buy more servers to run a slow front end than to spend extra on contractors to write it to run faster!

                  I led a team of java developers about 5 years ago who had to write really fast java code, it was not a real problem you just had to be really careful how do it - I'm not a techie so I can't tell you how.
                  Last edited by MPwannadecentincome; 26 January 2009, 13:20.
                  This default font is sooooooooooooo boring and so are short usernames

                  Comment


                    #19
                    Originally posted by MPwannadecentincome View Post
                    Well that depends, as someone else said, you can write slow ram eating code in any language.

                    a common mistake is to forget to run the live system with '-server' on the JVM!

                    I know lots of enterprise systems running in java - these are scaleable systems processing thousands of transactions a minute.

                    One thing that is bad though is building web forms - this is a slow development task even with struts or whatever the latest fad is, in this respect PHP is much more productive and this needs to be balanced against the speed of the resulting system, it may be cheaper to buy more servers to run a slow front end than to spend extra on contractors to write it to run faster!

                    I led a team of java developers about 5 years ago who had to write really fast java code, it was not a real problem you just had to be really careful how do it - I'm not a techie so I can't tell you how.
                    A common mistake is to not charge for 4 weeks performance tuning work while only adding -server to the JVM.

                    Comment


                      #20
                      Originally posted by MPwannadecentincome View Post
                      Well that depends, as someone else said, you can write slow ram eating code in any language.

                      a common mistake is to forget to run the live system with '-server' on the JVM!

                      I know lots of enterprise systems running in java - these are scaleable systems processing thousands of transactions a minute.

                      One thing that is bad though is building web forms - this is a slow development task even with struts or whatever the latest fad is, in this respect PHP is much more productive and this needs to be balanced against the speed of the resulting system, it may be cheaper to buy more servers to run a slow front end than to spend extra on contractors to write it to run faster!

                      I led a team of java developers about 5 years ago who had to write really fast java code, it was not a real problem you just had to be really careful how do it - I'm not a techie so I can't tell you how.
                      The best way to write fast code in Java is to keep your code simple, the JVM can optimise simple code that it understands.

                      Java is used in real-time trading systems on Wall Street. It really is that quick, unless you listen to people (on here) who still judge in on 1995 benchmarks.

                      Good note about the -server flag. You can also change this in the JVM config file. I'd bet you're right that there is a lot of people not using this.

                      Comment

                      Working...
                      X