06-01-2011
Quote:
Originally Posted by
sixstrings
though I know windows has started to implement a similar strategy on its memory utilization.
I'm pretty sure Windows has been doing this for a long time. Its performance would be abysmal if it couldn't use disk cache. It just just shows cached mem as "free" to avoid the panic reaction we keep seeing elsewhere.
9 More Discussions You Might Find Interesting
1. Programming
Hi,
First of all I appreciate this group very much for its informative discussions and posts.
Here is my question.
I have one process whose virtual memory size increases linearly from 6MB to 12MB in 20 minutes. Does that mean my process has memory leaks?
In what cases does the... (4 Replies)
Discussion started by: shriashishpatil
4 Replies
2. UNIX for Advanced & Expert Users
I am running c++ code on AIX unix.I have a doubt that my code is using some memory but it is not clearing that.Some time i am getting heap allocation problem.In my code i am not using any malloc,new functions also i am justing using pointers and arrays.
Is there any way i can find out if the... (2 Replies)
Discussion started by: ukatru
2 Replies
3. UNIX for Advanced & Expert Users
I tried to execute a sample pthread program to cancel a newly created one using pthread_cancel(). but using valgrind on my code shows some memory leak.
My Code:
#include "iostream"
#include "unistd.h"
#include "pthread.h"
#include "signal.h"
using namespace std;
void handler(int);
void*... (4 Replies)
Discussion started by: kcr
4 Replies
4. Programming
I have this code...
#include <stdio.h>
#include <iostream>
#include <pthread.h>
static void* cliente(void *datos);
int main()
{
pthread_attr_t tattr;
int ret;
size_t size = PTHREAD_STACK_MIN + 0x0100;
ret = pthread_attr_init(&tattr);
ret =... (8 Replies)
Discussion started by: JEscola
8 Replies
5. UNIX for Advanced & Expert Users
Hi.
This might be a strange request, but does anyone have any idea on a simple shell script that would use more and more memory as it ran? Like a purposeful leak.
I want to test the behaviour of an already running program when the machine runs out of memory.
Thanks! (4 Replies)
Discussion started by: rebelbuttmunch
4 Replies
6. IP Networking
Hi All,
my client server application can work in two modes:
1) one direction - only client sends msgs to server
2) two directions - server gives 'answers' to client.
when program run in the first mode it looks OK, but when server answers to client than client's application exit its... (2 Replies)
Discussion started by: lenna
2 Replies
7. Programming
hi all
Can any one plz explain me about memory leak problem
Thankx (5 Replies)
Discussion started by: sonali
5 Replies
8. Programming
Hi,
I am trying a database server which keeps a B+ plus tree structure and works on it.
I am trying to find the memory used/leak while executing this process.
I check the memory leak by using ps uax command.
When i execute a delete query i am sure that my code frees up the existing... (9 Replies)
Discussion started by: kumaran_5555
9 Replies
9. Programming
I have written this code in C which reads a very large collection of text files and does some processing. The problem with this code is that there are memory leaks which I am not able to figure out as to where the problem is. When I run this code, and see the memory usage using top command, then I... (7 Replies)
Discussion started by: shoaibjameel123
7 Replies
LEARN ABOUT REDHAT
ldap_flush_cache
LDAP_CACHE(3) Library Functions Manual LDAP_CACHE(3)
NAME
ldap_enable_cache, ldap_disable_cache, ldap_destroy_cache, ldap_flush_cache, ldap_uncache_entry, ldap_uncache_request,
ldap_set_cache_options - LDAP client caching routines
SYNOPSIS
#include <ldap.h>
ldap_enable_cache( ld, timeout, maxmem )
LDAP *ld;
long timeout;
long maxmem;
void ldap_disable_cache( ld )
LDAP *ld;
void ldap_destroy_cache( ld )
LDAP *ld;
void ldap_flush_cache( ld )
LDAP *ld;
void ldap_uncache_entry( ld, dn )
LDAP *ld;
char *dn;
void ldap_uncache_request( ld, msgid )
LDAP *ld;
int msgid;
void ldap_set_cache_options( ld, opts )
LDAP *ld;
unsigned long opts;
DESCRIPTION
These routines are used to control the behavior of the experimental client caching of ldap_search(3) and ldap_compare(3) operations. By
default, the cache is disabled and no caching is done. Enabling the cache can greatly improve performance and reduce network bandwidth
when a client DUA makes repeated requests.
ldap_enable_cache() should be called to turn on local caching or to change cache parameters (lifetime of cached requests and memory used).
The ld parameter should be the result of a successful call to ldap_open(3). The timeout is specified in seconds, and is used to decide how
long to keep cached requests. The maxmem value is in bytes, and is used to set an upper bound on how memory the cache will use. You can
specify 0 for maxmem to restrict the cache size by the timeout only. The first call to ldap_enable_cache creates the cache; subsequent
calls re-enable the cache and set the timeout and memory values.
ldap_disable_cache() temporarily disables use of the cache (new requests are not cached and the cache is not checked when returning
results). It does not delete the cache contents.
ldap_destroy_cache() turns off caching and completely removes the cache from memory.
ldap_flush_cache() deletes the cache contents, but does not effect it in any other way.
ldap_uncache_entry() removes all requests that make reference to the distinguished name dn from the cache. It should be used, for example,
after doing an ldap_modify(3) call involving dn.
ldap_uncache_request() removes the request indicated by the LDAP request id msgid from the cache.
ldap_set_cache_options() is used to change caching behavior. The current supported options are LDAP_CACHE_OPT_CACHENOERRS to suppress
caching of any requests that result in an error, and LDAP_CACHE_OPT_CACHEALLERRS to enable caching of all requests. The default behavior
is to not cache requests that result in errors, except that request that result in the error LDAP_SIZELIMIT_EXCEEDED are cached.
ERRORS
ldap_enable_cache() returns 0 upon success, and -1 if it is unable to allocate space for the cache. All the other calls are declared as
void and return nothing.
SEE ALSO
ldap(3), ldap_search(3), ldap_compare(3)
ACKNOWLEDGEMENTS
OpenLDAP is developed and maintained by The OpenLDAP Project (http://www.openldap.org/). OpenLDAP is derived from University of Michigan
LDAP 3.3 Release.
OpenLDAP 2.0.27-Release 22 September 1998 LDAP_CACHE(3)