2011/3/29 Christoph Jasinski <christoph...@googlemail.com>:
> --
> You received this message because you are subscribed to the Google Groups
> "Express" group.
> To post to this group, send email to expre...@googlegroups.com.
> To unsubscribe from this group, send email to
> express-js+...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/express-js?hl=en.
>
--
regards,
Oleg Slobodskoi
--------------------------------------------------------------------
Xing: https://xing.com/profile/Oleg_Slobodskoi
Twitter: https://twitter.com/oleg008
Github: https://github.com/kof
--
You received this message because you are subscribed to the Google Groups "Express" group.
To post to this group, send email to expre...@googlegroups.com.
To unsubscribe from this group, send email to express-js+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/express-js?hl=en.
2011/3/29 Christoph Jasinski <christoph...@googlemail.com>:
> --
> You received this message because you are subscribed to the Google Groups
> "Express" group.
> To post to this group, send email to expre...@googlegroups.com.
> To unsubscribe from this group, send email to
> express-js+...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/express-js?hl=en.
>
--
This result shows that express is way faster than sinatra for a single
route that just echoes a string :) Probably not a result you could make
a technology choice on... bear in mind that if you are looking for
performance in a real application, you may decide to stick a memcache
in there, or if you are doing an API-only server, you will be load-balancing
it thru a queue system - so there are usual more moving parts that need
measuring.
> Havn't tried cluster yet. Seems very promising. But when you routing on a single process is already 4X faster than normal, it would speed up the cluster too.
Putting in a cluster will require the kind of caching and queuing I mention
above. Don't forget that if you have data persistence in the backend that
is going to add a performance hit.
So - you have to make a choice, but you don't have time to make
the kind of system that you need to measure to be accurately informed
about the choice - this happens to everyone - all you can do are look
at what's out there already and see how it goes for them
Here's an article on the Exceptional product's architecture, which I
found pretty cool, and it might be interesting for you to check out.
Interestingly, there's a note there about maybe moving to node.js
at some point...
http://blog.getexceptional.com/post/976830048/some-notes-about-our-new-api-implementation
cheers
--oh
--
Just saying you can't extrapolate from a string echo to a whole scalable
app. Neither can you even extrapolate from echoing a string to rendering
a layout/view -- the rendering code might be jet fast in the slow string
echoer and a dog in the fast string echoer :)
TJ did some of this kind of stuff in an oldish blog entry at
http://tjholowaychuk.com/post/543953703/express-vs-sinatra-benchmarks
which shows that your expectation of express.js being much better at
responses is pretty solid when you make it more realistic, i.e. including
haml/sass ports. There's yer proof ;)
cheers
--oh
Did you keep the code for the test around by any chance? I'll
volunteer to bring it up to date and run with the latest versions
of stuff.
--oh
Chris
On Wednesday, March 30, 2011, TJ Holowaychuk <tjholo...@gmail.com> wrote:
>
>
> unfortunately not, I had a script in express, then moved it to connect, and then removedit all together because it required quite a few dependencies to run correctly