Changes between Initial Version and Version 1 of Ticket #11216, comment 34


Ignore:
Timestamp:
2015-03-25T21:09:46+01:00 (11 years ago)
Author:
bastiK

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #11216, comment 34

    initial v1  
    2323> As a solution, maybe it would be the best, to move JCS initialization to "splash screen" so it will not introduce the problem later. Though having 20 second wait time at splash screen doesn't sound good either.
    2424
    25 JCS initialization at startup may be a good idea, as it can be done concurrently along with the other startup tasks. The 20 second probably sounds more dramatic than it is: It happened only once and I suspect another process caused the system to stress out. The delay was shorter most of the time, but still quite noticeable.
     25~~JCS initialization at startup may be a good idea, as it can be done concurrently along with the other startup tasks. The 20 second probably sounds more dramatic than it is: It happened only once and I suspect another process caused the system to stress out. The delay was shorter most of the time, but still quite noticeable.~~
     26
     27Edit: Probably not needed, see below.
    2628
    2729> > Another thing: Could you explain the relation of JCS memory cache and `MemoryTileCache`? Why do we need the JCS with 1000 keys, when the custom one is still used?