[GitHub] libcloud pull request: Cache locations to improve list_images perf...

2015-09-23 Thread relaxdiego
Github user relaxdiego closed the pull request at:

https://github.com/apache/libcloud/pull/544


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] libcloud pull request: Cache locations to improve list_images perf...

2015-07-07 Thread relaxdiego
GitHub user relaxdiego opened a pull request:

https://github.com/apache/libcloud/pull/544

Cache locations to improve list_images performance

This change caches the locations in a private attribute to avoid
repeated calls for the same result set. The number of calls made is
directly proportional to the number of images returned. For a 223
result set, this can reach as high as 99.990 seconds. Caching the
locations reduces it to around 2.001 seconds. The risk of stale location
data during execution is negligible.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/relaxdiego/libcloud optimize_list_images

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/544.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #544


commit cfc6d889e77f05b2ff972506c69449807eb98455
Author: Mark Maglana mmagl...@gmail.com
Date:   2015-07-07T20:56:09Z

Cache locations to improve list_images performance

This change caches the locations in a private attribute to avoid
repeated calls for the same result set. The number of calls made is
directly proportional to the number of images returned. For a 223
result set, this can reach as high as 99.990 seconds. Caching the
locations reduces it to around 2.001 seconds. The risk of stale location
data during execution is negligible.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---