Log Analyzer - Cache Users for Trace Flag Entities

Issue #1533 resolved
Justin Julicher created an issue

When setting trace flags for organisations with a large amount of users it would be good if this could be cached.

Comments (5)

  1. Scott Wells repo owner

    Yeah, this was discussed in #1417 as well. I do cache the users and classes for the duration of that dialog, but if you close it and reopen it then it has to run the query again. I don't cache it for longer than that because it gets into the whole issue of a cache expiration. I suppose I could keep track of when the most recent user was last modified and just run a query like:

    SELECT LastModifiedDate
    FROM User
    ORDER BY LastModifiedDate DESC
    LIMIT 1
    

    to determine whether to evict/repopulate the cache. I'll think about it a bit...

  2. Justin Julicher reporter

    That would be great - just updating the users but the last modified would make a great difference.

  3. Scott Wells repo owner

    I think this should have been resolved by changes that were made in the semi-recent (last 1-1.5 years) past. Let me know if you're still seeing performance issues.

  4. Log in to comment