Fix caching
burgerdev opened this issue · comments
Markus Rudy commented
- All caches should
provide the methods defined in interfaceimplement their respective interface properly (partial reason for ilastik/ilastik#807)OpCache
-
OpArrayCache
and parents -
OpCompressedCache
-
OpValueCache
(cannot be tracked reliably, see this post for example) - operators that act like caches (
OpLabelVolume
,OpFilterLabels
) - missing something?
-
- add an additional field "cache info" to
MemInfoNode
-
ArrayCacheMemoryManager
should be replaced byCacheMemoryManager
which- should manage
named cachesall 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)
- should manage
- remove deadlock possibilities (#79)
- fix report generation (#148)
-
fix priority calculation(#173) -
perhaps remove drtile?(#80) see #181 - extensive testing in ilastik
Markus Rudy commented
Progress see #160.
Markus Rudy commented
I think this is ready for being tested by other devs...
Markus Rudy commented
PR merged.