From: Hank K. <hkn...@gm...> - 2011-02-20 17:26:17
|
I recently read this commentary: "The major difference is that Mochiweb is faster and nimbler while Yaws handles more concurrent connections. Inets is only for local testing however." http://tinyurl.com/5votckb Are you in general agreement that Yaws is slower but handles more concurrent connections? I am simply serving a single small JavaScript file, generated dynamically with Erlang/Mnesia. |
From: Bob I. <bo...@re...> - 2011-02-20 18:16:04
|
The best thing to do would be to benchmark it with your application. There probably isn't going to be much difference between the two, and it should be easy to try them both with such a simple use case. On Mon, Feb 21, 2011 at 1:26 AM, Hank Knight <hkn...@gm...> wrote: > I recently read this commentary: > > "The major difference is that Mochiweb is faster and nimbler while > Yaws handles more concurrent connections. > Inets is only for local testing however." > http://tinyurl.com/5votckb > > Are you in general agreement that Yaws is slower but handles more > concurrent connections? > > I am simply serving a single small JavaScript file, generated > dynamically with Erlang/Mnesia. > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > Erlyaws-list mailing list > Erl...@li... > https://lists.sourceforge.net/lists/listinfo/erlyaws-list > |
From: Steve V. <vi...@ie...> - 2011-02-20 20:06:33
|
On Sun, Feb 20, 2011 at 12:26 PM, Hank Knight <hkn...@gm...> wrote: > I recently read this commentary: > > "The major difference is that Mochiweb is faster and nimbler while > Yaws handles more concurrent connections. > Inets is only for local testing however." > http://tinyurl.com/5votckb > > Are you in general agreement that Yaws is slower but handles more > concurrent connections? I doubt that's true. I've seen some people claim Yaws is faster while others claim Mochiweb is faster, but personally I'd guess they were about the same in both performance and connection handling. The one area where there might be a difference -- and let me stress the word "might," since I've never measured this specifically -- is for apps performing heavy file delivery, where I would guess Yaws could have an advantage in speed and lower CPU due to the sendfile driver. But that's only a guess, based on measuring Yaws without sendfile against Yaws with sendfile. Of course if Bob and the Mochiweb folks have ported the sendfile driver or written their own, there would be no difference in this area, either. And either way, someday relatively soon even that difference, if it exists, could be a moot point since Tuncer Ayaz is in the process of moving my sendfile driver into Erlang/OTP (and I'm helping him where I can), thus making it available to all web servers and other Erlang apps. > I am simply serving a single small JavaScript file, generated > dynamically with Erlang/Mnesia. I would guess they perform similarly for such an application. As Bob suggested, just measure them and decide for yourself which is more suitable for your app. One thing of which I am certain is that Bob won't be upset if you choose Yaws nor will Klacke and I be upset if you choose Mochiweb. ;-) --steve |