<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 19, 2013 at 6:34 AM, Daniel Bevenius <span dir="ltr"><<a href="mailto:daniel.bevenius@gmail.com" target="_blank">daniel.bevenius@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; "><div dir="ltr"><div class="im">><span style="font-family:arial,sans-serif;font-size:13px">I wonder what kind of numbers would we get by ditching JPA completely </span><span style="font-family:arial,sans-serif;font-size:13px">and using a non-relational DB like Redis</span></div>
<div>
<span style="font-family:arial,sans-serif;font-size:13px">Yeah, I think we will most likely need to if we want to come close to the other implementations performance wise. Others use Memcache and I've seen MongoDB in use as well. </span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px">Perhaps I should just add performance tests for the rest of the SimplePush operations so that we have them covered and then look into using a non-relational DB. Once that is done we can revisit this performance task.</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px">What do people thing about that?</span></div></div></blockquote><div><br></div></div></div></div></blockquote><div><br></div><div>Why not do something simpler first and validate that by adding a cache on the database access?</div><div><br></div></div></body></html>