Results 1 to 3 of 3
  1. #1
    Join Date
    May 2005
    Location
    South Africa
    Posts
    1,365
    Provided Answers: 1

    Unanswered: memory pool too small for current demands

    Any suggestions on how to handle this warning?

    07:00000:00263:2006/06/10 03:22:02.16 server The 4K memory pool of named cache default data cache (cache id 0, cachelet id 1) is configured too small for current demands (state 2). Transaction progress may cease or response time may increase.
    07:00000:00075:2006/06/10 06:50:47.82 server The 32K memory pool of named cache default data cache (cache id 0, cachelet id 1) is configured too small for current demands (state 2). Transaction progress may cease or response time may increase.

    Here are the current cache config
    Code:
     Cache Name                     Status    Type     Config Value Run Value    
     ------------------------------ --------- -------- ------------ ------------ 
     default data cache             Active    Default   13000.00 Mb  13000.00 Mb 
                                                       ------------ ------------
                                                Total    13000.0 Mb   13000.0 Mb   
    ==========================================================================
    Cache: default data cache,   Status: Active,   Type: Default
          Config Size: 13000.00 Mb,   Run Size: 13000.00 Mb
          Config Replacement: relaxed LRU,   Run Replacement: relaxed LRU
          Config Partition:            1,   Run Partition:            1
     IO Size  Wash Size Config Size  Run Size     APF Percent 
     -------- --------- ------------ ------------ ----------- 
         4 Kb 921600 Kb      0.00 Mb   9000.00 Mb     10      
        32 Kb 921600 Kb   4000.00 Mb   4000.00 Mb     10      
    (return status = 0)
    Version: ASE 12.5.3 on Solaris 8
    Sun Fire 880
    Memory size: 16384 Megabytes

  2. #2
    Join Date
    Feb 2002
    Location
    Willy is on vacation
    Posts
    1,208
    If you resized the pool on the fly. This only takes effect after a recycle. Thsi sort of is semi-dynamic

  3. #3
    Join Date
    May 2005
    Location
    South Africa
    Posts
    1,365
    Provided Answers: 1
    For your info:

    Problem fixed by changing Cache Replacement to strict LRU

    I also posted this on the sybase.public.ase.general group and it seems there is a bug using relaxed LRU

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •