Path: csiph.com!usenet.pasdenom.info!aioe.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed2.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
To: python-list@python.org
From: Mark Lawrence <breamoreboy@yahoo.co.uk>
Subject: Re: Finding size of Variable
Date: Sat, 08 Feb 2014 13:17:08 +0000
References: <8e4c1ab1-e65d-483f-ad9d-6933ae2052c3@googlegroups.com> <lcred6$q3r$1@ger.gmane.org> <mailman.6405.1391542145.18130.python-list@python.org> <7e7d3200-a4ae-4842-ad8d-68b4435b9006@googlegroups.com> <52f219c5$0$29972$c3e8da3$5496439d@news.astraweb.com> <mailman.6418.1391600696.18130.python-list@python.org> <acdae8c8-2b59-4289-9f2b-1e4dd52cbd62@googlegroups.com> <mailman.6441.1391685020.18130.python-list@python.org> <888bd2fc-54b0-4c46-9d7b-d81d01a78b52@googlegroups.com> <52f59aeb$0$29972$c3e8da3$5496439d@news.astraweb.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
In-Reply-To: <52f59aeb$0$29972$c3e8da3$5496439d@news.astraweb.com>
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.6538.1391865456.18130.python-list@python.org>
Lines: 60
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:65676

On 08/02/2014 02:48, Steven D'Aprano wrote:
> On Thu, 06 Feb 2014 05:51:54 -0800, wxjmfauth wrote:
>
>> Sorry, I'm only pointing you may lose memory when working with short
>> strings as it was explained. I really, very really, do not see what is
>> absurd or obsure in:
>>
>>>>> sys.getsizeof('abc' + 'EURO')
>> 46
>>>>> sys.getsizeof(('abc' + 'EURO').encode('utf-32'))
>> 37
>
>
> Why do you care about NINE bytes? The least amount of memory in any PC
> that I know about is 500000000 bytes, more than fifty million times more.
> And you are whinging about wasting nine bytes?
>
> If you care about that lousy nine bytes, Python is not the language for
> you. Go and program in C, where you can spent ten or twenty times longer
> programming, but save nine bytes in every string.
>
> Nobody cares about your memory "benchmark" except you. Python is not
> designed to save memory, Python is designed to use as much memory as
> needed to give the programmer an easier job. In C, I can store a single
> integer in a single byte. In Python, horror upon horrors, it takes 14
> bytes!!!
>
> py> sys.getsizeof(1)
> 14
>
> We consider it A GOOD THING that Python spends memory for programmer
> convenience and safety. Python looks for memory optimizations when it can
> save large amounts of memory, not utterly trivial amounts. So in a Python
> wide build, a ten-thousand block character string requires a little bit
> more than 40KB. In Python 3.3, that can be reduced to only 10KB for a
> purely Latin-1 string, or 20K for a string without any astral characters.
> That's the sort of memory savings that are worthwhile, reducing memory
> usage by 75%.
>
> Could Python save memory by using UTF-8? Yes. But it would cost
> complexity and time, strings would be even slower than they are now. That
> is not a trade-off that the core developers have chosen to make, and I
> agree with them.
>
>
>

This is a C +1 to save memory when compared against this Python +1 :)

-- 
My fellow Pythonistas, ask not what our language can do for you, ask 
what you can do for our language.

Mark Lawrence

---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com