in reply to Re^3: Gay Dating; or, Thrifty Set Intersections with an Accumulator
in thread Gay Dating; or, Thrifty Set Intersections with an Accumulator

s/Omega/Theta/, my bad.

It seems that you are refusing to acknowledge some basic reality checks in favor of theoretical purity.

N does not actually get to go to infinity, and neither does your budget of time, money, ram, disk space, network bandwidth, etc.

If you can't imagine when one network request and NlogN cpu cycles (EG: query a central server then figure out the sources from the data patterns) could be better than N network requests and N cpu cycles (EG: asking all the sources directly), then I am truly sorry for you.

Addendum: Consider also that you may want to not just think about, but actually implement both an O(NlogN) algorithm and an O(N2) for the same task. Then choose which one to run with an if (N > $breakEvenPoint) { $result = doNlogN() } else { $result = doNsquared() }

Replies are listed 'Best First'.
Re^5: Gay Dating; or, Thrifty Set Intersections with an Accumulator
by JavaFan (Canon) on Aug 12, 2010 at 21:12 UTC
    N does not actually get to go to infinity
    Actually, the entire point of "big-Oh" is to talk about behaviours of functions when taking limits.

    If one doesn't want to do so, don't mention "big-Oh".

      Getting Joe Watercooler to talk about big-Oh & etc correctly is about as likely as getting everybody to use proper code indentation...