Don't use hpx::util::static_ in topology code

[brycelelbach]

[reported by manderson] [Trac time Wed Mar 7 19:26:35 2012] If HWLOC_FOUND is ON, the scaling of the embarrassingly parallel application on ithaca looks like this:
./ep_client --scale 20 --number_partitions 1 --hpx:threads 1 takes 59.7 sec
./ep_client --scale 10 --number_partitions 2 --hpx:threads 2 takes 58.2 sec
./ep_client --scale 5 --number_partitions 4 --hpx:threads 4 takes 28.3 sec

When HWLOC_FOUND is OFF, the scaling becomes:

./ep_client --scale 20 --number_partitions 1 --hpx:threads 1 takes 59.6 sec
./ep_client --scale 10 --number_partitions 2 --hpx:threads 2 takes 29.1 sec
./ep_client --scale 5 --number_partitions 4 --hpx:threads 4 takes 14.2 sec

This is probably a bug somewhere explaining these results.

[brycelelbach]

[comment by heller] [Trac time Thu Mar 8 12:49:18 2012] The problem was that the threads were not pinned correctly. I pointed that out multiple
times and worked on that problem for the last couple of days.
The issue with hwloc has been fixed with 233f4ec.

[brycelelbach]

[comment by blelbach] [Trac time Fri Mar 9 18:39:30 2012] The use of static_ is still a problem, preventing applications from scaling.

[brycelelbach]

[comment by heller] [Trac time Fri Mar 9 18:41:10 2012] Bryce,
As I wrote in the emails, and in the comment above, hpx::util::static_ was not at all causing the scaling problems.
The problem was fixed with 233f4ec.

[brycelelbach]

[comment by blelbach] [Trac time Fri Mar 9 18:43:05 2012] This is not true. There are still scaling issues due to the use of static_. Benchmark embarrassingly parallel applications with and without HWLOC, for example, hpx_homogeneous_task_spawn. The pinning issue improved things but did not entirely fix them.