01-12-2012
What applications running there? Is SMT activated? What OS level do you have (latest fix pack installed?)? Is that always, only at peak times? What has changed since? More info would be helpful, thanks.
10 More Discussions You Might Find Interesting
1. Solaris
Hi to all,
i have an app on solaris 5.8 writed in C++ (3.2.1) that use multi threading.
Hardware has 8 cpu. When i run my app i note that the average of cpu go at least at 40%, and the performance are not so higher..
There is a cpu limitation on solaris, that dedicate only a part of cpu... (3 Replies)
Discussion started by: Moodie
3 Replies
2. Solaris
Hi All,
In my application malloc is returning NULL even though there is sufficient amount of free memory is available but swap memory is low.
Is this possible that, if free memory is high & swap memory is low, malloc will not be able to allocate memory & return NULL ?:)
Kindly look into... (5 Replies)
Discussion started by: Ritesh Kumar
5 Replies
3. Shell Programming and Scripting
on the file Ftp'd from the mainframe ,do we have any UNIX command to replace mainframe low and values to space or null.
i tried using tr and it doesn't work ...
Thanks (1 Reply)
Discussion started by: rlmadhav
1 Replies
4. Shell Programming and Scripting
Is it possible to have a bash script pick the highest and lowest values of four variables? I've been googling for this but haven't come up with anything. I have a script that assigns variables ($c0, $c1, $c2, and $c3) based on the coretemps from grep/sed statements of sensors. I'd like to also... (5 Replies)
Discussion started by: graysky
5 Replies
5. Shell Programming and Scripting
Hi guys,
i have a question about spliting a binary file into 2 chunks.
First chunk with all high bytes and the second one with all low bytes.
What unix tools can i use? And how can this be performed?
I looked in manpages of split and dd but this does not help.
Thanks (2 Replies)
Discussion started by: basta
2 Replies
6. HP-UX
There might be some problem with my server,
because every morning at 7, it's performance become bad with no DB extra deadlock.
But I just couldn't figure it out.
Please give me some advise, thanks a lot...
According to the CPU performace chart, Daily CPU loading Maximum: 42 %, Average:36%.
... (8 Replies)
Discussion started by: GreenShery
8 Replies
7. UNIX for Dummies Questions & Answers
Need some clarification on this....
1. how are kernel/ user spaces and high/low memory related?
2. What do they all mean when i have the kernel command line as:
"console=ttyS0,115200 root=/dev/sda2 rw mem=exactmap memmap=1M@0 memmap=96M@1M irqpoll"
or
2. what do mem and memmap mean in... (3 Replies)
Discussion started by: dragonpoint
3 Replies
8. AIX
Hi
I am running AIX 5.2. My server is running low on memory. It it using about 1307775 file pages on a total of 1511424 (from vmstat -v).
I looked at the memory yesterday morning, and we had plenty of free memory. I did a backup from Windows (ftp mget command) of a large file selection. From... (5 Replies)
Discussion started by: fredrivard
5 Replies
9. Red Hat
Hi team
I have three physical servers running on Red Hat Enterprise Linux Server release 6.2 with the following memory conditions:
# cat /proc/meminfo | grep -i mem
MemTotal: 8062888 kB
MemFree: 184540 kB
Shmem: 516 kB
and the following swap conditions:
... (6 Replies)
Discussion started by: hedkandi
6 Replies
10. UNIX for Advanced & Expert Users
Could I please get some recommendations of a linux live cd for low memory? (1 Reply)
Discussion started by: cokedude
1 Replies
LEARN ABOUT CENTOS
git-index-pack
GIT-INDEX-PACK(1) Git Manual GIT-INDEX-PACK(1)
NAME
git-index-pack - Build pack index file for an existing packed archive
SYNOPSIS
git index-pack [-v] [-o <index-file>] <pack-file>
git index-pack --stdin [--fix-thin] [--keep] [-v] [-o <index-file>]
[<pack-file>]
DESCRIPTION
Reads a packed archive (.pack) from the specified file, and builds a pack index file (.idx) for it. The packed archive together with the
pack index can then be placed in the objects/pack/ directory of a Git repository.
OPTIONS
-v
Be verbose about what is going on, including progress status.
-o <index-file>
Write the generated pack index into the specified file. Without this option the name of pack index file is constructed from the name of
packed archive file by replacing .pack with .idx (and the program fails if the name of packed archive does not end with .pack).
--stdin
When this flag is provided, the pack is read from stdin instead and a copy is then written to <pack-file>. If <pack-file> is not
specified, the pack is written to objects/pack/ directory of the current Git repository with a default name determined from the pack
content. If <pack-file> is not specified consider using --keep to prevent a race condition between this process and git repack.
--fix-thin
Fix a "thin" pack produced by git pack-objects --thin (see git-pack-objects(1) for details) by adding the excluded objects the
deltified objects are based on to the pack. This option only makes sense in conjunction with --stdin.
--keep
Before moving the index into its final destination create an empty .keep file for the associated pack file. This option is usually
necessary with --stdin to prevent a simultaneous git repack process from deleting the newly constructed pack and index before refs can
be updated to use objects contained in the pack.
--keep=<msg>
Like --keep create a .keep file before moving the index into its final destination, but rather than creating an empty file place <msg>
followed by an LF into the .keep file. The <msg> message can later be searched for within all .keep files to locate any which have
outlived their usefulness.
--index-version=<version>[,<offset>]
This is intended to be used by the test suite only. It allows to force the version for the generated pack index, and to force 64-bit
index entries on objects located above the given offset.
--strict
Die, if the pack contains broken objects or links.
--threads=<n>
Specifies the number of threads to spawn when resolving deltas. This requires that index-pack be compiled with pthreads otherwise this
option is ignored with a warning. This is meant to reduce packing time on multiprocessor machines. The required amount of memory for
the delta search window is however multiplied by the number of threads. Specifying 0 will cause Git to auto-detect the number of CPU's
and use maximum 3 threads.
NOTE
Once the index has been created, the list of object names is sorted and the SHA-1 hash of that list is printed to stdout. If --stdin was
also used then this is prefixed by either "pack ", or "keep " if a new .keep file was successfully created. This is useful to remove a
.keep file used as a lock to prevent the race with git repack mentioned above.
GIT
Part of the git(1) suite
Git 1.8.3.1 06/10/2014 GIT-INDEX-PACK(1)