ilastik / lazyflow

lazy parallel ondemand zero copy numpy array data flows with caching and dirty propagation

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Fix caching

burgerdev opened this issue · comments

  1. All caches should provide the methods defined in interface OpCache implement their respective interface properly (partial reason for ilastik/ilastik#807)
    • OpArrayCache and parents
    • OpCompressedCache
    • OpValueCache (cannot be tracked reliably, see this post for example)
    • operators that act like caches (OpLabelVolume, OpFilterLabels)
    • missing something?
  2. add an additional field "cache info" to MemInfoNode
  3. ArrayCacheMemoryManager should be replaced by CacheMemoryManager which
    • should manage named caches all caches that explicitly state that they want to be managed
    • should be started explicitly, not by importing some file (allow non-cache applications to not have a daemon thread for caches)
  4. remove deadlock possibilities (#79)
  5. fix report generation (#148)
  6. fix priority calculation (#173)
  7. perhaps remove drtile? (#80) see #181
  8. extensive testing in ilastik

Progress see #160.

I think this is ready for being tested by other devs...

PR merged.