Horizon reloads properties of all containers when changed only one

[Kyrylo Romanenko]

Horizon reloads properties of all containers when object in one container updated. This will create high excessive load when big number of containers is used.
Steps:
1. Create several Containers via Horizon -> Object Store.
2. Create 1 object in any 1 container.
3. Just after creation of object Horizon will re-load properties of every available container.

VERSION:
  feature_groups:
    - mirantis
  production: "docker"
  release: "6.1"
  openstack_version: "2014.2.2-6.1"
  api: "1.0"
  build_number: "500"
  build_id: "2015-06-03_04-06-47"
  nailgun_sha: "3830bdcb28ec050eed399fe782cc3dd5fbf31bde"
  python-fuelclient_sha: "4fc55db0265bbf39c369df398b9dc7d6469ba13b"
  astute_sha: "cbae24e9904be2ff8d1d49c0c48d1bdc33574228"
  fuel-library_sha: "938f033a5da90aca0c24c89c995cf01707d746d2"
  fuel-ostf_sha: "f899e16c4ce9a60f94e7128ecde1324ea41d09d4"
  fuelmain_sha: "bcc909ffc5dd5156ba54cae348b6a07c1b607b24"

[Timur Nurlygayanov (tnurlygayanov)]

Looks like important issue for Horizon performance, we also have to commit this fix to upstream

[Paul Karikh (pkarikh)]

I'm think it is an expected behaviour. That's how Horizon works now: after some action on page Horizon reloads it with second GET request to this page. Sure, it is not optimal, but it is a comman way in Horizon to handle such requests.

[Timur Sufiev (tsufiev-x)]

I'd add that it's how the rendering of separate table entries are done in Swift UI vs. regular Horizon table entries: each container entry is being updated asynchronously on the very first load of Swift UI, while regular Horizon table contents are fetched first from the server-side and then rendered as the whole html chunk. To remedy this behaviour we'll have to rework the most basic rendering of Swift UI - or just throw away an old code and rewrite it with Angular. The latter approach seems more appropriate to me.