Comments on: Vimagi Speedups

By: Yariv

Yariv — Thu, 22 Nov 2007 21:13:43 +0000

I agree this benchmark would be very interesting. I’m curious, too, how ErlyWeb’s performance compares to other frameworks’. However, I have a few other things on my plate right now so I can’t promise I’ll do this benchmarking in the near future. It would be great if someone else volunteered to do it.

By: Andy

Andy — Wed, 21 Nov 2007 12:40:10 +0000

I’d love to see some benchmark data of ErlyWeb against other frameworks. Would love to see if all the claims of performance and scalability holds up. Not that I’m skeptical, but empirical data is always nice :)

ErlyWeb against PHP, JSP, RoR, Python, .NET, and some Java framework would be awesome.

Please do it!

By: Yariv

Yariv — Wed, 21 Nov 2007 07:42:48 +0000

You didn't need to recompile ErlyDB -- you can pass a different log function into erlydb:start() which only logs errors and warnings. This is the function I use in Vimagi, for instance:



log(Module, Line, Level, FormatFun) ->

    case Level of

        debug ->

            ok;

        _ ->

            Func = case Level of

                       info ->

                           info_msg;

                       normal ->

                           info_msg;

                       error ->

                           error_msg;

                       warn ->

                           warning_msg

                   end,

            {Format, Params} = FormatFun(),

            error_logger:Func("~w:~b: "++ Format,

                              [Module, Line | Params])

    end.

I haven't tried using HiPE. After removing the auto_compile flag, I think the site is fast enough. Some day, when I benchmark ErlyWeb against other frameworks, I'll use HiPE :)

By: Bryan

Bryan — Mon, 19 Nov 2007 22:55:00 +0000

Nicely done on the speedups. BeerRiot is the same: all dynamically generated with almost no caching yet. I’ve written some skeleton code to handle it in places I expect it to be useful, but I’ve left it out for simplicity’s sake so far.

The only other thing I’ve done to my production system is recompiled ErlyDB such that it doesn’t try to print out every SQL command. I don’t know that I’ve seen a lot of speedup from that change, but it seemed unnecessary to send debugging messages to a console that isn’t even attached.

Have you tried recompiling with HiPE yet? Developing on PPC Mac and deploying on x86 Linux, I wasn’t sure if I’d see any discontinuities, so I haven’t gone down that path yet.