Networks

General discussion

Gravatar
Locked

NW6 56% cachebuffer system with 3gig ram

By david.silva ·
When originally installed last summer, this system reported 72% cache buffers. Currently it is dipping into the mid to low 50s. Not too much loaded, SP2, base NW6 services, BackupExec v9, plus NDPS. No native file access, no iprint, no ifolder etc. I have searched the Knowledgebase for memory leak TIDS, and have updated the TSA to beta 11, latest NSS and NDPS patches.

Files system is NSS with 2 pools, total storage is 70g with about 25g of files. 15 active connections.

When I reboot the server, it starts at 56% cache buffer and in 30 minutes or so goes up to 70%, then sometime during the day that decreases again to 56%.

Any ideas? Seems I should have more available with this much memory installed.

Thanks -David

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
+ Follow this Discussion ·
| Thread display: Collapse - | Expand +

All Comments

gravatar
Collapse -

NW6 56% cachebuffer system with 3gig ram

by deroode In reply to NW6 56% cachebuffer syste ...

Check the knowledgebase for NSS cache consumption. Free cache buffers are only used for traditional volumes. NSS cache is taken from the original cache buffers. Now when installing NSS volumes you should reserve enough cache memory for NSS, which means that reported cache buffers will be less. When it is configured properly this is not a problem, but mainly an indication that NSS has also enough cache memory.

gravatar
Collapse -

NW6 56% cachebuffer system with 3gig ram

by david.silva In reply to NW6 56% cachebuffer syste ...

I don't think it's NSS. Looking at Resource Management this morning, NSS is consuming 90 MB, but NWMKDE is consuming 464 MB in small memory allocations. There is one tid on this for NW 5.1 relating to a corrupted bti.lck file, but there is no such file on the NW6 system.

gravatar
Collapse -

NW6 56% cachebuffer system with 3gig ram

by BudTheGrey In reply to NW6 56% cachebuffer syste ...

Another sneaky RAM thief is btreive -- use the web portal to see how much ram NWMKDE is allocating. During install, it seems to use some kind of hard coded "I'm gonna take x% of the available ram" algorithm. Look for the file BTI.INI (in sys:system, IIRC) and modify accordingly. You'll probably have to reboot after making the changes.

gravatar
Collapse -

NW6 56% cachebuffer system with 3gig ram

by david.silva In reply to NW6 56% cachebuffer syste ...

Problem indeed was btrieve ( NWMKDE.NLM ). The bti.cfg file had cache settings of 209624 which resulted in small allocation consumption of 460MB in NWMKDE - and server allocated memory of 1.3GB!!! Trimming the BTI cach to 104812 brought the NWMKDE small allocation size down to 360MB, and the server allocated memory down to 500MB! There must be something strange happening when NWMKDE consumes more than 360MB (SP2) to account for the difference in server allocated memory.

Cache sizes need to be in this range as btrieve is also being used as a db engine for the client's accounting application.

Thanks for pointing me in the right direction!

gravatar
Collapse -

NW6 56% cachebuffer system with 3gig ram

by david.silva In reply to NW6 56% cachebuffer syste ...

This question was closed by the author

Back to Networks Forum
5 total posts (Page 1 of 1)  

Start or search

Related Discussions

Related Forums