Topic:   Anyone with a better idea on how to use redis pub sub for cache invalidation? Any POC reference would be appreciated
Nov 07, 2020 03:47 4 Replies 605 Views SAI

Anyone with a better idea on how to use redis pub sub for cache invalidation? Any POC reference would be appreciated

Prev Next
Topic Replies (4)
  1. 1
    idnkx user

    PADMAKEECHU

    what do you mean by cache invalidation ? it's about Gc and memory managment ?

    1
    idnkx user

    PADMAKEECHU

    I have set up a redis cache that can cache files into redis memory, but I am looking for something that can notify my servers whenever the files has been edited and delete it from the cache so my servers would stop getting outdated files from cache memory. Does that make sense to you?

    1
    idnkx user

    FRAUSKY

    you have to set your servers a better way.
    It's kind of full copies...
    a sort by Date ? or by Version of files could stand as a solution ?
    ospf protocol uses a list about IPs and Paths, sometimes refreshing... and renewing... LDAP ??
    LDAP have great 'behavior' for lists and mutlicast of resources

    1
    idnkx user

    FRAUSKY

    as I think the problem was 'memory space', I have wrote all that ... I keep it here.
    what are ceil and floor about your memories usage ?
    during sessions ( for one ? more ? )
    looks for ceil creators, here are codes to rewrite,
    or to balance through a secondary Thread...
    or a Task to destroy when work is done.
    Gc is member of resources, so auto-completion and its package will show some tools
    see what "= Nothing" does as a endpoint for var like Objects ( but wide ones ), it's strict memory use and syntax.
    .Net is great thing, but automation about memory ends when Gc is under efficiency.. ( Gc my best and worst ennemy )
    really cross to full oop, it's about allocation and fast access, so is the .Net structured and favorite.
    a simple pattern :
    // start of a loop
    initiate
    do
    destroy
    // end of the loop
    It works with var and objects ( all in ) too
    It's about reducing memories involved, Threads have a max amount of all too
    keep on scrutating the 0 down line of CPU / Ram ...
    a mountain appears ? and stay as high rate and uses...
    put it down, really.
    considers 'work size in Go / Mo / Ko'.
    Once load, once unload.

Leave a Reply
Guest User

Not sure what course is right for you?

Choose the right course for you.
Get the help of our experts and find a course that best suits your needs.


Let`s Connect