Performance vs OpenResty about lapis HOT 4 CLOSED

I actually haven't done any real performance benchmarking yet. I think the numbers you got are pretty reasonable for a starting point. I made a couple optimizations in terms of lazy loading information but I think there's still a lot of room for improvement.

from lapis.

I'm not very familiar with Openresty (still learning), but wouldn't using nginx for routing speed things up?

Have lapis server load web.lua, with a dummy lapis.serve method, that extracts the paths, and writes them in nginx.conf.compiled. Something like

        location /foo {
            default_type text/html;
            content_by_lua "handlers['foo'](uri_parser['foo'](uri))";
        }

You'd load Lapis with init_by_lua_file, to register the handlers.

from lapis.

Hi, I saw you mentioned the TechEmpower framework benchmark on lapis' homepage, but I haven't seen any of it done with lapis, only with OpenResty.

So I just wrote the first three test. It's doing quite well, I get a few thousand req/s for the first two and about 200-1300 for the third on my rather slow dev machine. (Nevertheless, OpenResty is easily 3x as fast for the "hello world" JSON benchmark, since it seems to have far less overhead.)

You can find the code here. Fork it if you'd like to extend or fix it; it's essentially your code anyway. :)

I'd be happy to see lapis in the next round of framework benchmarks, especially if it also had implementations for the other ORM tests.

from lapis.

Closing old discussion

from lapis.