What you are seeing is most likely file system caching. Solaris considers unused memory a waste, so it parks (caches) data read from files or written to files in memory because it improves performance. The kernel will release file caches anytime there is a need for more memory.
Last edited by jim mcnamara; 12-18-2012 at 11:36 AM..
Could someone point me in the correct direction or web link containing instructions for installing the System Performance Tool (aka STP) software on an IBM-AIX version 4.? machine. My client has the software (that came from their original server) on a 3" floppy. Thanks! (1 Reply)
I'm running Solaris 8 on a Sun ULTRA 5(SPARC II CPU, 270 MHz) with 64 Mb of RAM.
The machine is very, very slow even doing normal tasks such as reading mail....... I'm nearly afraid to ask it to do some real work.......
On checking out the machine(which I only received last week from our IT... (1 Reply)
I need to prepare script which will run as background process ever 30 mins to collect the following information
1. Memory usage.
2. CPU usage.
3. Number processors running.
4. System resource (CPU and Memory) used by each process.
5. Number of sessions logged
PLEASE HELP ME OUT FROM THIS
... (2 Replies)
Anyone know how to fetch the system performance information by the function except the system command? These information includes CPU load,memory usage,network load,disk capacity,etc. (5 Replies)
I have received an order from upper level manager to "verify system information via Perform/predict'. They asks me to *predict* the system performance. How can I do it as a system admin without the help of application admins and DBAs?
Thanks! (6 Replies)
Dear experts ,
Pls advice for any good Tool to monitor the CPU and performance of AIX the system ..
to keep monitoring to show me the utilization of that system .. (12 Replies)
hi every body i want to check system performance i usually use glance,top,sar and swapinfo but i confused in something so i need explanation about memory issue
first i want check the memory usage i used glance i found this parameter so i need one shows me the differences between these... (2 Replies)
Discussion started by: maxim42
2 Replies
LEARN ABOUT DEBIAN
bup-margin
bup-margin(1) General Commands Manual bup-margin(1)NAME
bup-margin - figure out your deduplication safety margin
SYNOPSIS
bup margin [options...]
DESCRIPTION
bup margin iterates through all objects in your bup repository, calculating the largest number of prefix bits shared between any two
entries. This number, n, identifies the longest subset of SHA-1 you could use and still encounter a collision between your object ids.
For example, one system that was tested had a collection of 11 million objects (70 GB), and bup margin returned 45. That means a 46-bit
hash would be sufficient to avoid all collisions among that set of objects; each object in that repository could be uniquely identified by
its first 46 bits.
The number of bits needed seems to increase by about 1 or 2 for every doubling of the number of objects. Since SHA-1 hashes have 160 bits,
that leaves 115 bits of margin. Of course, because SHA-1 hashes are essentially random, it's theoretically possible to use many more bits
with far fewer objects.
If you're paranoid about the possibility of SHA-1 collisions, you can monitor your repository by running bup margin occasionally to see if
you're getting dangerously close to 160 bits.
OPTIONS --predict
Guess the offset into each index file where a particular object will appear, and report the maximum deviation of the correct answer
from the guess. This is potentially useful for tuning an interpolation search algorithm.
--ignore-midx
don't use .midx files, use only .idx files. This is only really useful when used with --predict.
EXAMPLE
$ bup margin
Reading indexes: 100.00% (1612581/1612581), done.
40
40 matching prefix bits
1.94 bits per doubling
120 bits (61.86 doublings) remaining
4.19338e+18 times larger is possible
Everyone on earth could have 625878182 data sets
like yours, all in one repository, and we would
expect 1 object collision.
$ bup margin --predict
PackIdxList: using 1 index.
Reading indexes: 100.00% (1612581/1612581), done.
915 of 1612581 (0.057%)
SEE ALSO bup-midx(1), bup-save(1)BUP
Part of the bup(1) suite.
AUTHORS
Avery Pennarun <apenwarr@gmail.com>.
Bup unknown-bup-margin(1)