[Lift] Re: What happens between 7000 and 8000 requests?
Yes indeed. I have an plus of ~317%. Thanks again. On Jan 21, 3:34 pm, David Pollak feeder.of.the.be...@gmail.com wrote: On Thu, Jan 21, 2010 at 6:25 AM, Stefan Koenig koeni...@gmail.com wrote: First of all thanks for the replies. Your comments made a lot of sense, so I tested again using a cookie jsessionid and voilà no problems anymore even running more than 100,000 requests in a row now. Also the failed requests are gone. And is Lift still much faster? Thanks again. Stefan Koenig On Jan 21, 5:16 am, Derek Williams de...@nebvin.ca wrote: Okay, I tried it out. jsessionid is sometimes 12 or 13 characters long which is why the document length is changing. Those failures due to length are probably safe to ignore. On Wed, Jan 20, 2010 at 6:00 PM, Derek Williams de...@nebvin.ca wrote: I could be wrong here, but I think the failed requests might be due to the jsessionid that jetty adds onto the links, they may be different sizes. I am away from my computer right now and can't test it though. -- Derek Williams -- You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.comliftweb%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/liftweb?hl=en. -- Lift, the simply functional web frameworkhttp://liftweb.net Beginning Scalahttp://www.apress.com/book/view/1430219890 Follow me:http://twitter.com/dpp Surf the harmonics -- You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
[Lift] Re: What happens between 7000 and 8000 requests?
First of all thanks for the replies. Your comments made a lot of sense, so I tested again using a cookie jsessionid and voilà no problems anymore even running more than 100,000 requests in a row now. Also the failed requests are gone. Thanks again. Stefan Koenig On Jan 21, 5:16 am, Derek Williams de...@nebvin.ca wrote: Okay, I tried it out. jsessionid is sometimes 12 or 13 characters long which is why the document length is changing. Those failures due to length are probably safe to ignore. On Wed, Jan 20, 2010 at 6:00 PM, Derek Williams de...@nebvin.ca wrote: I could be wrong here, but I think the failed requests might be due to the jsessionid that jetty adds onto the links, they may be different sizes. I am away from my computer right now and can't test it though. -- Derek Williams -- You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
[Lift] What happens between 7000 and 8000 requests?
Hey everyone, I'm very new to lift, so maybe this is just some production-flip I don't know about, but I made a few performance tests Lift vs. Rails and I was a bit surprised that with my configuration Rails won (for a high number of requests). As I said I'm new to Lift, but am using Rails since late 2005 and have various projects in production, also managing a few of my own servers. So what I want to say is: Compared to Rails I know nothing about deploying applications effective in Lift. So that's obviously unfair. For testing I used two very basic hello world-like applications, trying to serve the same HTML, with a little layout handling on both sides. For Rails I chose Thin server which is more or less on par with Passenger+NginX stack I use in production (and I know Thin is being used in production environment). For Lift I took the Jetty server which came out of the box and I read Jetty is often being chosen over Tomcat for production. (I couldn't find any obvious deploy guide.) After Testing: Lift is indeed faster (+ ~93%) in a low number of requests 7000, but something happens between 7000 and 8000 requests which puts lift into trouble (Threadpool full?). Another finding is that the CPU usage of Lift was much higher, than the one of Rails, even in a low number of requests. (I added screenshots of the CPU usage in the repository) So basically my questions: Did I do something wrong? What happens between 7000 and 8000 requests? You can find all of the data here: http://github.com/koenig/testlift/ Thank you, Stefan Koenig -- You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
