profiling

The problem is that behavioral profiling will get better.

Understanding what causes performance issues and how to use Xcode's profiling tools is useful too.

Compine that with the new integrated performance/memory profiling tools and it's a slam dunk.

If anything this shows how inaccurate and thus non-threatening this kind of profiling is.

Clarkson acknowledges that racial profiling at airports is racist, and says that we should do it anyway.

There are a lot of approaches around (big data, profiling, machine learning,...) based on the assumption that people usually behave in the same way.

Using clang to compile, I did some profiling on my function optimized to various levels (-O0...-O3, -Os, -Ofast) with various inputs.

Also great for performance profiling when you don't have fancy tools.

By the way, you are mistaken if you think that a large number of other airports systematically engage in racial profiling as a matter of policy.

I guess that can be healthy since that plug-in is undoubtedly used for Google's own profiling to somehow sell more ads, heh.

How is the profiling data supposed to be used theoretically?

And wouldn't a correction for this itself cause a much more disturbing racist exercise ie; profiling every possible data point against race and forever maintaining such profiles?

It wouldn't create much positive publicity, but the most honest way would be a "pay for privacy" option where you have to pay a monthly sum in order to disable the data collection, profiling, data selling and targeted advertising.

I added code profiling to rwasa so that you can run load tests against it and watch call graphs and individual function timings, which makes for interesting inspection of the library itself for specific "tricks" that were employed.

Profiling on OSx being broken is another (and this isn't the fault of the GO, but rather apple.