> Hmmm... I don't know, redis is famous for crunching somewhere in the order > of 500K requests per-second - have you tested it? > I though it was clear, anyway, I reinstate: yep, it was clearly loosing performances each step of complexity added. I'm a big fan of NoSQL but please do mind that relational engines are backed by tenths of years of development and millions of testing users. NoSQL strips out some of the major complexities of relational engines to work at warp speed. If you need a really small subset of operation than by any mean, NoSQL are a cool addition to the toolbelt. However when you start adding cool features of relational engines to NoSQL (basically reinventing the wheel) performances drop considerably.
-- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
