yahoo-eng-team team mailing list archive

[Ben Nemec <openstack@xxxxxxxxxxxx>]

The in-memory cache isn't intended for production use anyway, so we
don't want to spend a bunch of time optimizing it.

** Changed in: oslo
       Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1276530

Title:
  memorycache#get scans the whole cache for expired items on every fetch

Status in OpenStack Compute (Nova):
  Triaged
Status in Oslo - a Library of Common OpenStack Code:
  Won't Fix

Bug description:
  Every time an item is fetched from the memory cache, the whole cache
  is scanned for expired items:

  https://github.com/openstack/nova/blob/master/nova/openstack/common/memorycache.py#L63-L67

  This is not the right place to expire items - a large cache can become
  slow.  There should be a more sensible approach to the (difficult)
  problem of cache expiry.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1276530/+subscriptions