Sponsored Content
Operating Systems AIX AIX memory usage by processes Post 303025194 by Corona688 on Friday 26th of October 2018 12:02:14 PM
Old 10-26-2018
Try ps -e -o size -o args= | sort -k 1,1 which is a very, very rough estimate that likely includes a lot of overlap between processes.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Memory Usage in AIX

Hi All, I have a question, can you guys please help me by giving your valuable suggestons: I am using AIX 5L, running oracle 7 version. I need to increase the oracle memory to 40 MB more. Currently Oracle occupies 260M. I wanted to know whether I can increase the memory without any problem.... (1 Reply)
Discussion started by: kollam68
1 Replies

2. AIX

Memory Usage in AIX

Hi All, I have a question, can you guys please help me by giving your valuable suggestons: I am using AIX 5L, running oracle 7 version. I need to increase the oracle memory to 40 MB more. Currently Oracle occupies 260M. I wanted to know whether I can increase the memory without any problem.... (3 Replies)
Discussion started by: kollam68
3 Replies

3. AIX

High memory usage in AIX 5.1

Hi, We have AIX 5.1 machine of RAM 8 GB and paging space is 8GB. we are getting high memory usage of almost 99%.Can anybody please help in this ? Partial vmstat o/p kthr memory ----- ----------- r b avm fre 2 1 278727 1143 There is no paging issue.Becoz in... (5 Replies)
Discussion started by: jayakumarrt
5 Replies

4. AIX

estimating memory usage by database processes

Hi Guys, I wonder what would be the best way to determine how much memory is in use on any given time by the database processes. I thought about using ipcs -m command but I wonder if there any better way to determine this. Thanks. Harby. (2 Replies)
Discussion started by: hariza
2 Replies

5. AIX

Memory usage on AIX

How to check the memory usage on AIX by various processes? (1 Reply)
Discussion started by: aajmani
1 Replies

6. AIX

How to monitor the IBM AIX server for I/O usage,memory usage,CPU usage,network..?

How to monitor the IBM AIX server for I/O usage, memory usage, CPU usage, network usage, storage usage? (3 Replies)
Discussion started by: laknar
3 Replies

7. AIX

AIX 5.3 Physical Memory usage

Hi, I have AIX 5.3TL8 two node cluster using HACMP and have 10g database using RAW devices. I am seeing gradual increase in comp% memory everyday and it reaches 100% and evicts the node, we had 4 evictions in 40days. I am pasting vmstat and vmo output, anyone seen this issue? ... (5 Replies)
Discussion started by: navin7386
5 Replies

8. AIX

AIX memory usage always high

hi, I want to ask , my AIX 6.1 is always used about 97% memory. Is this normal ? or any command can free up memory like Linux ? thanks. (1 Reply)
Discussion started by: virusxx
1 Replies

9. AIX

Identify All Processes memory and cpu usage.

Hi All, Anyone has script to monitor AIX total processes memory and cpu usage that contribute to the total memory and CPU utilize so far ? The purpose of this is to analyze process memory trend. Thanks. Best Regards, ckwan (2 Replies)
Discussion started by: ckwan
2 Replies

10. AIX

Memory usage in AIX server

Hi All, I have some questions regarding the performance, MEMORY/ Virtual Memory (paging /swap space) Please see the nmon-MEMORY stats from my AIX LPAR. 24 GB --> RAM 3456 MB --> Paging Space │ Memory ─────────────────────────────────────────────────────────────────────── │... (8 Replies)
Discussion started by: System Admin 77
8 Replies
MAKEHISTORY(8)						    InterNetNews Documentation						    MAKEHISTORY(8)

NAME
makehistory - Initialize or rebuild INN history database SYNOPSIS
makehistory [-abeFIOx] [-f filename] [-l count] [-T tmpdir] DESCRIPTION
makehistory rebuilds the history(5) text file, which contains a list of message IDs of articles already seen by the server. It can also be used to rebuild the overview database. Note that the dbz(3) indexes for the history file are rebuilt by makedbz(8), not by makehistory as in earlier versions of INN. The default name of the history text file is pathdb/history; to specify a different name, use the -f flag. By default, makehistory will scan the entire spool, using the storage manager, and write a history line for every article. To also gener- ate overview information, use the -O flag. WARNING: If you're trying to rebuild the overview database, be sure to delete or zero out the existing database before you start for the best results. Otherwise, you may end up with problems like out-of-order overview entries, excessively large overview buffers, and the like. If you are using ovdb as your overview method, you will want to have the ovdb processes running while rebuilding overview; otherwise, the Berkeley DB transaction logs will be extremely large by the time makehistory finishes. You can start them with dbprocs(8). OPTIONS
-a Append to the history file rather than generating a new one. If you append to the main history file, make sure innd(8) is throttled or not running or you can corrupt the history. -b Delete any messages found in the spool that do not have valid Message-ID headers in them. -e Compute Bytes headers which is used for overview data. This option is valid only if -O flag is specified and overview.fmt includes "Bytes:". -f filename Rather than writing directly to pathdb/history, instead write to filename. -F Fork a separate process to flush overview data to disk rather than doing it directly. The advantage of this is that it allows makehis- tory to continue to collect more data from the spool while the first batch of data is being written to the overview database. The dis- advantage is that up to twice as much temporary disk space will be used for the generated overview data. This option only makes sense in combination with -O. With "buffindexed", the "overchan" program is invoked to write overview. -I Don't store overview data for articles numbered lower than the lowest article number in active(5). This is useful if there are old articles on disk for whatever reason that shouldn't be available to readers or put into the overview database. -l count This option specifies how many articles to process before writing the accumulated overview information out to the overview database. The default is 10000. Since overview write performance is faster with sorted data, each "batch" gets sorted. Increasing the batch size with this option may further improve write performance, at the cost of longer sort times. Also, temporary space will be needed to store the overview batches. At a rough estimate, about 300 * count bytes of temporary space will be required (not counting temp files created by sort(1)). See the description of the -T option for how to specify the temporary storage location. This option has no effect with "buffindexed", because "buffindexed" does not need sorted overview and no batching is done. -O Create the overview database as well as the history file. Overview information is only required if the server supports readers; it is not needed for a transit-only server. If you are using the "buffindexed" overview storage method, erase all of your overview buffers before running makehistory with -O. -T tmpdir If -O is given, makehistory needs a location to write temporary overview data. By default, it uses pathtmp, set in inn.conf(5), but if this option is given, the provided tmpdir is used instead. This is also used for temporary files created by sort(1) (which is invoked in the process of writing overview information since sorted overview information writes faster). By default, sort usually uses /var/tmp; see the man page for sort on your system to be sure. -x If this option is given, makehistory won't write out history file entries. This is useful mostly for building overview without gener- ating a new history file. EXAMPLES
Here's a typical example of rebuilding the entire history and overview database, removing broken articles in the news spool. This uses the default temporary file locations and should be done while innd isn't running or is throttled. makehistory -b -f history.n -O -l 30000 -I This will rebuild the overview (if using "buffindexed", erase the existing overview buffers before running this command) and leave a new history file in history.n in pathdb. To preserve all of the history entries from the old history file that correspond to rejected articles or expired articles, use: cd /usr/local/news/db awk 'NF == 2 { print }' < history >> history.n (replacing the path with your pathdb, if it isn't the default). Then look over the new history file for problems and run: makedbz -s `wc -l < history` -f history.n Then rename all of the files matching "history.n.*" to "history.*", replacing the current history database and indexes. After that, it's safe to unthrottle innd. For a simpler example: makehistory -b -f history.n -I -O will scan the spool, removing broken articles and generating history and overview entries for articles missing from history. To just rebuild overview: makehistory -O -x -F FILES
inn.conf Read for pathdb and pathtmp. pathdb/history This is the default output file for makehistory. pathtmp Where temporary files are written unless -T is given. HISTORY
Originally written by Rich $alz <rsalz@uunet.uu.net> for InterNetNews and updated by various other people since. $Id: makehistory.8,v 1.26.2.6 2002/08/25 23:58:41 rra Exp $ SEE ALSO
dbz(3), active(5), history(5), inn.conf(5), dbprocs(8), ctlinnd(8), innd(8), makedbz(8). INN 2.3.4 2002-08-25 MAKEHISTORY(8)
All times are GMT -4. The time now is 12:35 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy