From 18657a960e125336f704ea058e25c27bd3900dcb Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sun, 5 May 2024 19:28:19 +0200 Subject: Adding upstream version 3.40.1. Signed-off-by: Daniel Baumann --- www/c3ref/memory_highwater.html | 151 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 151 insertions(+) create mode 100644 www/c3ref/memory_highwater.html (limited to 'www/c3ref/memory_highwater.html') diff --git a/www/c3ref/memory_highwater.html b/www/c3ref/memory_highwater.html new file mode 100644 index 0000000..5fffd0e --- /dev/null +++ b/www/c3ref/memory_highwater.html @@ -0,0 +1,151 @@ + + + + + +Memory Allocator Statistics + + + +
+ + + +
+
+Small. Fast. Reliable.
Choose any three. +
+
+ +
+ +
+
+ + + +
+
+
+ + +
+

SQLite C Interface

 +

Memory Allocator Statistics

+
+
+sqlite3_int64 sqlite3_memory_used(void);
+sqlite3_int64 sqlite3_memory_highwater(int resetFlag);
+
+

+SQLite provides these two interfaces for reporting on the status +of the sqlite3_malloc(), sqlite3_free(), and sqlite3_realloc() +routines, which form the built-in memory allocation subsystem.

+ +

The sqlite3_memory_used() routine returns the number of bytes +of memory currently outstanding (malloced but not freed). +The sqlite3_memory_highwater() routine returns the maximum +value of sqlite3_memory_used() since the high-water mark +was last reset. The values returned by sqlite3_memory_used() and +sqlite3_memory_highwater() include any overhead +added by SQLite in its implementation of sqlite3_malloc(), +but not overhead added by the any underlying system library +routines that sqlite3_malloc() may call.

+ +

The memory high-water mark is reset to the current value of +sqlite3_memory_used() if and only if the parameter to +sqlite3_memory_highwater() is true. The value returned +by sqlite3_memory_highwater(1) is the high-water mark +prior to the reset. +

See also lists of + Objects, + Constants, and + Functions.

+ -- cgit v1.2.3