[DOCU-2237] Mention that cache for arbitrary objects is not suiteable for high performance IO operations Created: 16/Sep/21 Updated: 10/Nov/21 Resolved: 10/Nov/21 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | 6.2.6 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Marty Glaubitz | Assignee: | Martin DrĂ¡pela |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | cache | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Ubuntu |
||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Task DoR: |
Empty
|
||||
| Date of First Response: | |||||
| Description |
|
I tried to migrate the caching solution for our custom external DAM connector to the build-in cache mechanism, instead of using the Caffeine library. I was hoping to give us thus easier controll over manual initiated cache flushes. However i had to discover that all read/write operations are blocking and thus requests which load a lot of assets became unbarably slow, as well as throwing a lot of exceptions about caches beeing locked. This is certainly nothing one wants to deal with when trying to optimize such operations and the documentation (https://docs.magnolia-cms.com/product-docs/6.2/Modules/List-of-modules/Cache-modules/Caching-arbitrary-objects.html) should mention this. Idealy the underlying issue of the caches probally hving multi-threading issues, should be solved |
| Comments |
| Comment by Marty Glaubitz [ 22/Sep/21 ] |
|
Okay, i will have a look at it |