on 05-08-2014 9:50 AM
Dear experts,
We are facing the following error, accompanied by slow performance and full disk utilization:
06:00000:00620:2014/05/08 00:55:56.99 server The 8K memory pool of named cache default data cache (cache id 0, cachelet id 1) is configured too small for current demands (state 1). Transaction progress may cease or response time may increase.
Case History:
This error was noticed with the standard 2K pool
We configured another 8K Pool, same error appeared for the 8K pool
Configured additional 16K pool, same error faced for the 16K pool
Removed the 16K pool
Increased the 8K pool
Error still appear for the 8K pool now and performance still very slow
No other programs are running on server except Sybase ASE
Disk utilization is monitored using "glance"
ASE version: 12.5.3
OS: HP-UX 11.23
sp_cacheconfig now:
Cache Name Status Type Config Value Run Value
---------- ------ ---- ------------ ---------
default data cache Active Default 15360.00 Mb 15360.00 Mb
IO Size Wash Size Config Size Run Size APF Percent
------- --------- ----------- -------- -----------
2 Kb 245760 Kb 0.00 Mb 13312.00 Mb 10
8 Kb 245760 Kb 2048.00 Mb 2048.00 Mb 10
Dear Peter,
I have come across similar error (The 128K memory pool of named cache default data cache is configured too small for current demands... )
Acc to SAP the root cause of the error is:
97% Prefetch data Size is bigger than 128k pool size, So it can't use the Large I/Os pool.
This cause the message in errorlog "server The 128K memory pool of named cache default data cache ...."
Suggestion was given to increase the "128 K" memory pool size to 5GB
sp_poolconfig "default data cache", "5G", "128K"
go
HTH
Rajesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Rajesh,
There was an operating system kernel parameter that was recommended to be changed by the O.S. support, when changed, performance got enhanced.
O.S. Unix [HP-UX]
Parameter: hires_timeout_enable=1
Actually I'm not UNIX admin and I don't know exactly what this parameter does, but it enhanced the overall performance of the nightly batch that was taking much time.
BR | Peter
Hi Peter, Mark,
I'm fairly new to ASE. But we are seeing a very similar log. The output of sp_cacheconfig is below:
Cache Name Status Type Config Value Run Value
------------------ -------- -------- -------------- ------------
default data cache Active Default 8.00 Mb 8.00 Mb
(1 row affected)
------------ ------------
Total 8.00 Mb 8.00 Mb
==========================================================================
Cache: default data cache, Status: Active, Type: Default
Config Size: 8.00 Mb, Run Size: 8.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
-------- ------------- ------------ ------------ -----------
16 Kb 1632 Kb 8.00 Mb 8.00 Mb 10
(return status = 0)
LRU is already set to strict.
What was the problem and how did you finally solve it?
Regards,
Roy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.