07-03-2010
Is the OS 32-bit or 64-bit? In a 32-bit program, the per-process maximum memory limit is 4GB no matter how much more the OS may have available.
9 More Discussions You Might Find Interesting
1. Programming
For example if i have the piece of code as follows:
CountryName = (char *)malloc((strlen(CountryName)+1)*sizeof(char));
memset(CountryName, 0, strlen(CountryName)+1);
CountryName = SOME VALUE
Now how do i free the memory after use of this code???? :confused: (3 Replies)
Discussion started by: jazz
3 Replies
2. AIX
Hi,
how to find free memory in aix? for installing oracle,I have used svmon but not getting proper output (1 Reply)
Discussion started by: manoj.solaris
1 Replies
3. 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
4. Solaris
Hi all,
Could please let me know how to get the more memory free space (not added the RAM) in local zone.
-bash-3.00# vmstat 2 5
kthr memory page disk faults cpu
r b w swap free re mf pi po fr de sr s0 s1 s1 s1 in sy cs us sy... (3 Replies)
Discussion started by: murthy76
3 Replies
5. Red Hat
hi, I have done the below, but am confused as to how much memory is "free"
please help
thanks
$ free
total used free shared buffers cached
Mem: 132033488 48827536 83205952 0 1007696 45404632
-/+ buffers/cache: 2415208 ... (7 Replies)
Discussion started by: JamesByars
7 Replies
6. Web Development
Any clues on how to get rid of this PHP error?
PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 71 bytes) in /website/www/includes/functions_manpages.php on line 58
PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 71... (4 Replies)
Discussion started by: Neo
4 Replies
7. Shell Programming and Scripting
While running script I am getting an error like
Few lines in data are not being processed.
After googling it I came to know that adding such line would give some memory to it
ini_set("memory_limit","64M");
my input file size is 1 GB.
Is that memory limit is based on RAM we have on... (1 Reply)
Discussion started by: elamurugu
1 Replies
8. Programming
Hi guys.
I've a question, if we are using a syscall that receives a string allocated dynamicaly to a determined size, or NUL and it will allocate the apropriate size. We should free the memory or the OS will do it for us?
If a function returns a pointer we should free that poiter when we are done... (7 Replies)
Discussion started by: pharaoh
7 Replies
9. Shell Programming and Scripting
I have two files:
1. A huge 8 GB text file. (big_file.txt)
2. A huge list of words approximately 8 million of them. (words_file.txt). Each word is separated by a newline.
What I intend to do is to read each word "w" from words_file.txt and search for that word in big_file.txt. Then extract two... (12 Replies)
Discussion started by: shoaibjameel123
12 Replies
LEARN ABOUT DEBIAN
chi::driver::memory
CHI::Driver::Memory(3pm) User Contributed Perl Documentation CHI::Driver::Memory(3pm)
NAME
CHI::Driver::Memory - In-process memory based cache
VERSION
version 0.54
SYNOPSIS
use CHI;
my $hash = {};
my $cache = CHI->new( driver => 'Memory', datastore => $hash );
my $cache = CHI->new( driver => 'Memory', global => 1 );
DESCRIPTION
This cache driver stores data on a per-process basis. This is the fastest of the cache implementations, but data can not be shared between
processes. Data will remain in the cache until cleared, expired, or the process dies.
To maintain the same semantics as other caches, references to data structures are deep-copied on set and get. Thus, modifications to the
original data structure will not affect the data structure stored in the cache, and vica versa. See CHI::Driver::RawMemory for a faster
memory cache that sacrifices this behavior.
CONSTRUCTOR OPTIONS
When using this driver, the following options can be passed to CHI->new() in addition to the CHI. One of datastore or global must be
specified, or else a warning (possibly an error eventually) will be thrown.
datastore [HASHREF]
A reference to a hash to be used for storage. Within the hash, each namespace is used as a key to a second-level hash. This hash may
be passed to multiple CHI::Driver::Memory constructors.
global [BOOL]
Use a standard global datastore. Multiple caches created with this flag will see the same data. Before 0.21, this was the default
behavior; now it must be specified explicitly (to avoid accidentally sharing the same datastore in unrelated code).
DISCARD POLICY
For CHI/SIZE AWARENESS caches, this driver implements an 'LRU' policy, which discards the least recently used items first. This is the
default policy.
SEE ALSO
CHI::Driver::RawMemory, CHI
AUTHOR
Jonathan Swartz <swartz@pobox.com>
COPYRIGHT AND LICENSE
This software is copyright (c) 2011 by Jonathan Swartz.
This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.
perl v5.14.2 2012-05-30 CHI::Driver::Memory(3pm)