Very cool! Architecturally, is there a standard way to prevent exponential blowup when comparing all profiles to all profiles? I’d imagine some heuristics lik

Very cool! Architecturally, is there a standard way to prevent exponential blowup when comparing all profiles to all profiles? I’d imagine some heuristics like only comparing profiles within some geobounds. Potentially gender as well. Maybe a batch job that runs nightly and then accepting certain stale conditions but updating others on-demand? I’ve become more interested in the abstraction of this kind of n-way profile comparison recently but am not sure I’m using the right words and have trouble searching.