Results 1 to 2 of 2
  1. #1
    Join Date
    Feb 2009
    Posts
    6

    Unanswered: Sybase 12.5.3 limit cpu

    Hi,

    have in my cfg file to allow resource limits 1, it's possibile set parameter to 0 ?

    has impact ?

    this ase server has 8gb of ram assigned into file cfg, but I do not think it uses all the ram

    Can you help me please and sorry for my english dirty

    Thank's
    Gianluca

  2. #2
    Join Date
    Jun 2009
    Location
    South Africa
    Posts
    33
    The "allow resource limits" config parameter has nothing to do with the memory usage on ASE.

    It allows you to set up Engine (CPU) groups and time ranges and then bind resource usage parameters for users and applications to fall within those time ranges.
    A typical example would be to not allow large reports during normal office hours, where any query will be terminated if it exceeds say, more than 100000 IO operations.

    You need to look at the cache configuration, which will likely still by default be set to 8mb.

    Run "sp_configure memory" and look at the output of that :
    Code:
    Parameter Name                 Default     Memory Used Config Value Run Value   Unit                 Type       
    --------------                 -------     ----------- ------------ ---------   ----                 ----       
    additional network memory                0           0           0            0 bytes                dynamic    
    allocate max shared memory               0           0           0            0 switch               dynamic    
    heap memory per user                  4096           0        4096         4096 bytes                dynamic    
    lock shared memory                       0           0           0            0 switch               static     
    max memory                           48128     4096000     2048000      2048000 memory pages(2k)     dynamic    
    memory alignment boundary             2048           0        2048         2048 bytes                static     
    memory per worker process             1024           4        1024         1024 bytes                dynamic    
    messaging memory                       400           0         400          400 memory pages(2k)     dynamic    
    shared memory starting address           0           0           0            0 not applicable       static     
    total logical memory                 48128     2815852     1407926      1407925 memory pages(2k)     read-only  
    total physical memory                    0     2815856           0      1407928 memory pages(2k)     read-only  
    
    Configuration option is not unique.
     
    An additional 1280150 K bytes of memory is available for reconfiguration. This is the difference between 'max memory' and 'total logical memory'.
    (11 rows affected)
    (return status = 1)
    What you are interested in, is the "max memory", "total logical memory" and "total physical memory" parameters.
    In the example above, we have max memory set to 4Gb, but we have only allocated about 2.8 Gb to the current configuration.
    The message also indicates that we have roughly 1.2 Gb available for reconfiguration.

    Max memory = The maximum amount of memory that the ASE server will be allowed to use.
    Total Physical Memory = The amount of memory that ASE is currently using
    Total Logical Memory = The amount of memory that ASE will use, based on the current configuration parameters. Physical & Logical should be very close if the server was just restarted, and/or no config changes were done since the last restart.

    If sp_configure memory shows a large chunk not being used, your best bet would be to allocate the available memory to data caches and / or procedure cache.

    Look at the output from sp_cacheconfig:
    Code:
     Cache Name                     Status    Type     Config Value Run Value
     ------------------------------ --------- -------- ------------ ------------
     default data cache             Active    Default    2048.00 Mb   2048.00 Mb
                                                       ------------ ------------
                                                Total    2048.00 Mb   2048.00 Mb
    ==========================================================================
    Cache: default data cache,   Status: Active,   Type: Default
          Config Size: 2048.00 Mb,   Run Size: 2048.00 Mb
          Config Replacement: strict LRU,   Run Replacement: strict LRU
          Config Partition:            1,   Run Partition:            1
     IO Size  Wash Size Config Size  Run Size     APF Percent
     -------- --------- ------------ ------------ -----------
         2 Kb  50790 Kb      0.00 Mb   1348.00 Mb     10
         4 Kb  61440 Kb    200.00 Mb    200.00 Mb     10
        16 Kb  61440 Kb    500.00 Mb    500.00 Mb     10
    From this you can see that we have only one data cache, the 'default data cache', and that we have allocated 2Gb of memory to that. If I really want to use the extra 1.2 Gb of memory, the best bet would typically be to assign it to the 'default data cache', assuming that all the other config parameters are set to acceptable values.

    Use sp_monitorconfig "parameter" to verify config parameters and their usage stats, like 'sp_monitorconfig locks' , or 'open objects', 'open databases', open indexes' etc. :
    Code:
    Name                      Num_free    Num_active  Pct_act Max_Used    Num_Reuse   
    ----                      ----------- ----------- ------- ----------- ----------- 
    number of locks                 74681         319   0.43        14255           0 
    number of open objects           3276        1724  34.48         1731           0 
    number of open indexes           3982        6018  60.18         6024           0 
    number of open databases            4          16  80.00           16           0 
    number of user connection         193           7   3.50           20           0
    Number of locks is set to 75000, max used is 14255, so we have plenty in reserve. The metadata caches are also fine, as we have enough free resources there.
    User connections is set to 200, but we only ever used 20.
    A bit of wasted memory on some of these parameters if memory is really tight.

    Look at allocating a large chunk of the remaining memory to data caches in this case.

    Edit : Fixed typo in Par. 2.
    Last edited by Lerac; 07-29-09 at 15:47.

Posting Permissions

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