Comment 10 for bug 618367

I tried changing this to a 2-query form.

https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1711S60 is an example of the result.

In a different oops (-59) it does execute both queries, and we could see that on the SQL side it is slower (2 seconds vs 800ms) and on the python side it is /slightly/ faster.

In thie linked oops, (ignore the SQL time: 1001297 ms, Non-sql time: -981318 ms) figures - they are due to the sentinel showing the non-run query at the end - there is a clear 12 second gap between:
 - the execute returning to storm
 - the query for Person being executed.

So parsing the 3000 narrower rows(Specification only) took 12 seconds (including pulling out their related people IDs and building the next query) under the profiler (vs 16 for the very fat rows). This suggests a storm bug to me and I'm going to follow up on the storm bug I filed as a result of the first profile.