Popular recipes tagged "memory" but not "management"

Compute Memory footprint of an object and its contents (Python)

2012-11-23T23:57:31-08:00

Python recipe 577504 by Raymond Hettinger (memory, sizeof). Revision 3.

Recursive version sys.getsizeof(). Extendable with custom handlers.

Finding the sizes of various Python data types (Python)

2016-04-28T18:28:59-07:00

Python recipe 580655 by Vasudev Ram (data, datastructures, memory, python, python2, system, type).

This recipe shows how to find the sizes of various common data types in Python, both built-in and user-defined. It uses the sys.getsizeof() function and also discusses a few other points of interest.

Compute Memory footprint of an object and its contents (Python)

2014-05-15T13:44:15-07:00

Python recipe 578880 by yota (memory, sizeof).

Recursive version sys.getsizeof(). Extendable with custom handlers.

InMemoryZip class (Python)

2013-09-23T06:44:23-07:00

Python recipe 578667 by Thomas Lehmann (file, memory, path, zip).

Why implementing this?

transfering a file or a folder (including sub folders) to another machine
therefore zipping content to one compressed buffer
keeping the relating ZIP in memory only but ...
being able to save or load too
and being able to unzip again at target destination

Get memory usage of Windows processes using GetProcessMemoryInfo (via ctypes) (Python)

2013-04-25T01:26:19-07:00

Python recipe 578513 by Ben Hoyt (ctypes, memory, process, win32, windows).

These functions call the Win32 function GetProcessMemoryInfo() using ctypes to get the memory usage of the current process. Works on both 32-bit and 64-bit Windows and Python 2.6+ (including Python 3.x).

Human readable file/memory sizes (Python)

2012-11-05T11:59:20-08:00

Python recipe 578321 by Tony Flury (formatting, memory, size). Revision 5.

In writing a application to display the file sizes of set of files, I wanted to provide a human readable size rather then just displaying a byte count (which can get rather big).

I developed this useful short recipe that extends the format specifier mini Language to add the S presentation type - which will intelligently convert the value to be displayed into a known human readable size format - i.e. b, Kb,Mb, Gb etc. It honours the rest of the format specification language (http://docs.python.org/2/library/string.html#format-string-syntax)

It uses a factor of 1024 at each stage

Human readable file/memory sizes v2 (Python)

2012-11-11T17:28:57-08:00

Python recipe 578323 by Tony Flury (formatting, memory, size).

In writing a application to display the file sizes of set of files, I wanted to provide a human readable size rather then just displaying a byte count (which can get rather big).

I developed this useful short recipe that extends the format specifier mini Language to add new presentation type s- which will intelligently convert the value to be displayed into a known human readable size format - i.e. b, Kb,Mb, Gb, B, KB etc. It honours the rest of the format specification language (http://docs.python.org/2/library/string.html#format-string-syntax)

It uses a factor of 1024 for IEC and common formats, and factor of 1000 for SI units.

For AMIGA-Heads Only. Poking A HW, (Memory), Address On A Classic AMIGA, Inside Text Mode Python. (Python)

2012-09-09T19:25:00-07:00

Python recipe 578255 by Barry Walker (amiga, demo, e_uae, hardware, memory, poke, winuae).

For AMIGA-Heads Only...

This code is purely for a minimum of a stock Classic AMIGA A1200(HD), E-UAE, and WinUAE running AMIGA OS3.0x to 3.1x. It will NOT work on any other platform!

(It MIGHT work on AMIGA OS3.5x and 3.9x with Python 2.4.6, but totally untested and I hold no responsibility for the outcome when trying it.)

It is a DEMO to poke a byte inside _ANY_ memory address inside the standard CPU 68EC020 16MB boundary.

This is not a function nor a class but just a DEMO to show how to write directly to HW, (or memory), addresses.

POKING memory or hardware addresses is not recommended for novices without studying the machine first, and, this code will ignore any _ENFORCER_hits_.

I experimented with this several years ago and have decided to finally release it. I do await the flak!

It works from Python Versions 1.4.0 to 2.0.1 for the classic AMIGA.

This is issued as Public Domain and you may do with it as you please.

Ensure that the T: Volume exists on the running machine.

See inside the code and text below it also as to how it works...

Bazza, G0LCU...

Named Sequences for environments containing large numbers of POD instances (Python)

2010-11-27T13:55:18-08:00

Python recipe 577473 by Kevin L. Sitze (decorator, memory, sequence, slot, unittests).

Generate classes with named data attributes that can be sequenced. Useful for POD classes for which many records will exist concurrently.

Compare the feature set to NamedTuples by Raymond Hettinger: http://code.activestate.com/recipes/500261-named-tuples/

Size of Python objects (revised). (Python)

2017-07-22T15:52:01-07:00

Python recipe 546530 by Jean Brouwers (getsizeof, memory, sizeof). Revision 21.

This recipe determines the size of Python objects in bytes and has been further enhanced to handle ints, namedtuples, arrays and NumPy types better. Functions alen and itemsize have been updated. Support for Python 2.5 and earlier and the tests/examples have been removed. See project Pympler for unit tests.

See also other, simpler recipes like this Compute memory footprint of an object and its contents.

Reading large files from zip archive (Python)

2009-08-17T10:24:40-07:00

Python recipe 576882 by Volker S. (large_files, memory, zip). Revision 3.

The standard zipfile module provides only a method to extract the entire content of a file from within a zip-file. This extension adds a generator method to iterate over the lines in a file, avoiding the memory problems.

Track new/unreclaimed objects between 2 points in the code (Python)

2008-10-03T12:14:52-07:00

Python recipe 576523 by david decotigny (cycle, garbage, leak, memory, reclaim). Revision 3.

This module provides 3 ways of detecting which objects have been allocated (methods 1 and 3) or became un-reclaimable (method 2) between 2 points in the code. It can be very useful to detect memory leaks (eg. cycles involving objects with a __del__ method).