Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision |
pecl:apc:todo:40 [2009/10/15 05:52] – Add fine-grained locking research todo item shire | pecl:apc:todo:40 [2009/10/21 18:39] – add hash stats and file hash perf. todo shire |
---|
| Windows locking | Not Started | 4.0.0b | shire, pierre, kalle | Sounds like we need to look at our options for windows locking so we have a good, stable, efficient option that works on both Win and Unix flavors. Spin locks would be my first choice, but we need testing of support on windows and improvement of the signal handling problem for stability. | | | Windows locking | Not Started | 4.0.0b | shire, pierre, kalle | Sounds like we need to look at our options for windows locking so we have a good, stable, efficient option that works on both Win and Unix flavors. Spin locks would be my first choice, but we need testing of support on windows and improvement of the signal handling problem for stability. | |
| Virtual Host/Location | In-Progress/Partial | 4.0.0a | shire | With multiple cache support, the idea of separating files or user cache values based upon the virtual host or location became easier to support. Add a location or virtual host option to the per-cache configuration, essentially what the file cache filters option currently supports on the 4.x branch. This will automatically limit or direct file/user entries to the appropriate cache. | | | Virtual Host/Location | In-Progress/Partial | 4.0.0a | shire | With multiple cache support, the idea of separating files or user cache values based upon the virtual host or location became easier to support. Add a location or virtual host option to the per-cache configuration, essentially what the file cache filters option currently supports on the 4.x branch. This will automatically limit or direct file/user entries to the appropriate cache. | |
| | Hash stats/improve file hash | Not started | 4.0.0b | shire | We currently don't have stats for our hash collisions/performance, so we should add some stats that can be enabled/disabled here without affecting performance. We should then eval. the performance of the hash() function used for file device/inode and see if it should be more robust or if it's current performance is acceptable | |
| |
====== Research ====== | ====== Research ====== |