<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">On 22 Aug 2018, at 19:39, Sam <<a href="mailto:perl@net153.net" class="">perl@net153.net</a>> wrote:<div class=""><div><blockquote type="cite" class=""><div class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">This seems like a simple schema, not sure what caching would buy you unless the DB is not a local service on the same box or network (or getting several hundred requests per second). </span></div></blockquote><div><br class=""></div><div>Yeah, it's definitely getting hundreds of requests a second :)</div><br class=""><blockquote type="cite" class=""><div class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">Generally, in my apps when it comes to more complex queries, I first write the query in raw SQL and benchmark it. Then I convert it over to a DBIC resultset (which normally means using the prefetch option) and bench mark that. If it much slower than the raw SQL query, I might look into only fetching the columns I need (via the 'columns => []' property). If that doesn't speed it up enough, I'll then switch to using the hashref inflator resultsource class which usually brings it right in line raw SQL performance.</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""></div></blockquote></div><br class=""></div><div class="">Right, of course. But that doesn't making a compelling case to migrate to DBIC class. I already have an ad-hoc SQL version which has been benchmarked and optimised. It's the abstraction that I want.</div><div class=""><br class=""></div><div class="">Thanks.</div><div class=""><br class=""></div><div class=""><br class=""></div></body></html>