Jeff Chen wrote:
> One of these queries that should be targeting something like 300K
> photos takes 38 seconds to run (with an aggregate/nested loop
> taking effectively all of that time),
With the seek time of commodity disk drives typically being 9ms, a
naive approach using random access to jo
On 28.10.2014 22:15, Jeff Chen wrote:
> Hi friends!
>
> I'd love to get a sanity check on whether a fat select query I'm doing
> makes sense given the infrastructure that we have.
>
> We have 3 big tables that we typically join together for certain
> queries: a ~40 million row photos table, a ~20
Hi friends!
I'd love to get a sanity check on whether a fat select query I'm doing
makes sense given the infrastructure that we have.
We have 3 big tables that we typically join together for certain queries: a
~40 million row photos table, a ~20 million row users table, and a ~50
million row phot
