05-25-2009
Did you checked for deconfigured memory in 'ASMI' menu??
10 More Discussions You Might Find Interesting
1. HP-UX
Refer from title:
How can i get memory used or anything that can show memory from sar file
example on solaris:-
we can use sar with option to show memory used at time that sar crontab run.
on HP-UX, it not has option to see memory used. But i think it may be have some parameter or some... (1 Reply)
Discussion started by: panithat
1 Replies
2. Solaris
Hi,
Im working on Solaris 9 on SPARC-32 bit running on an Ultra-80, and I have to find out the following:-
1. Total Physical Memory in the system(total RAM).
2. Available Physical Memory(i.e. RAM Usage)
3. Total (Logical) Memory in the system
4. Available (Logical) Memory.
I know... (4 Replies)
Discussion started by: 0ktalmagik
4 Replies
3. Programming
Hi,
I'm trying to learn how to manage memory when I have to deal with lots of data.
Basically I'm indexing a huge file (5GB, but it can be bigger), by creating tables that
holds offset <-> startOfSomeData information. Currently I'm mapping the whole file at
once (yep!) but of course the... (1 Reply)
Discussion started by: emitrax
1 Replies
4. Solaris
Is it possible to restrict physical memory in solaris zone with zone.max-locked-memory just like we can do with rcapd ? I do not want to used rcapd (1 Reply)
Discussion started by: fugitive
1 Replies
5. UNIX for Dummies Questions & Answers
Hello,
I am trying to free memory allocation after EOF from keyboard is detected (ctrl+D) in a C program. I've written a small program to replicate my problem:
int main(int argc, char *argv) {
char *line;
line = (char*)malloc(sizeof(char)*(512));
line = fgets(line, 512,... (1 Reply)
Discussion started by: oddworld
1 Replies
6. Programming
Hello,
I am trying to free memory allocation after EOF from keyboard is detected (ctrl+D) in a C program. I've written a small program to replicate my problem:
int main(int argc, char *argv) {
char *line;
line = (char*)malloc(sizeof(char)*(512));
line = fgets(line, 512,... (10 Replies)
Discussion started by: oddworld
10 Replies
7. UNIX for Advanced & Expert Users
I was running a program and it stopped and showed "Out of Memory!". at that time, the RAM used by this process is around 4G and the free memory size of the machine is around 30G. Does anybody know what maybe the reason? this program is written with Perl. the OS of the machine is Solaris U8. And I... (1 Reply)
Discussion started by: lilili07
1 Replies
8. Solaris
Hello solaris experts,
Being new to solaris containers, from Linux, feeling difficulty in understanding certain concepts. Hope somebody can help me here.
I understand that, & some questions ....
Locked memory -- memory which will not be swapped out at any cause.
is this for... (0 Replies)
Discussion started by: thegeek
0 Replies
9. Solaris
Hi Experts,
Our servers running Solaris 10 with SAP Application. The memory utilization always >90%, but the process on SAP is too less even nothing.
Why memory utilization on solaris always looks high?
I have statement about memory on solaris, is this true:
Memory in solaris is used for... (4 Replies)
Discussion started by: edydsuranta
4 Replies
10. AIX
memory is more than 80% how will u trouble shoot it? (1 Reply)
Discussion started by: ramraj731
1 Replies
LEARN ABOUT DEBIAN
kiokudb::backend::role::txn::memory
KiokuDB::Backend::Role::TXN::Memory(3pm) User Contributed Perl Documentation KiokuDB::Backend::Role::TXN::Memory(3pm)
NAME
KiokuDB::Backend::Role::TXN::Memory - In memory transactions.
SYNOPSIS
with qw(KiokuDB::Backend::Role::TXN::Memory);
sub commit_entries {
my ( $self, @entries ) = @_;
# atomically apply @entries
# deleted entries have the deleted flag set
# if an entry has no 'prev' entry it's an insert
# otherwise it's an update
}
DESCRIPTION
This backend provides in memory transactions for backends which support atomic modification of data, but not full commit/rollback support.
This backend works by buffering all operations in memory. Entries are kept alive allowing read operations go to the live entry even for
objects that are out of scope.
This implementation provides repeatable read level isolation. Durability, concurrency and atomicity are still the responsibility of the
backend.
REQUIRED METHODS
commit_entries
Insert, update or delete entries as specified.
This operation should either fail or succeed atomically.
Entries with "deleted" should be removed from the database, entries with a "prev" entry should be inserted, and all other entries
should be updated.
Multiple entries may be given for a single object, for instance an object that was first inserted and then modified will have an insert
entry and an update entry.
get_from_storage
Should be the same as "get" in KiokuDB::Backend.
When no memory buffered entries are available for the object one is fetched from the backend.
exists_in_storage
Required as of KiokuDB version 0.37.
A fallback implementation is provided, but should not be used and will issue a deprecation warning.
perl v5.12.4 2010-10-11 KiokuDB::Backend::Role::TXN::Memory(3pm)