I'm unsure exactly what getsizeof() returns. __size__() also seems an odd function to have for a tasklet. But there is more in a tasklet thatn just the tasklet's object. Typically there probably is also a frame, arguments, and such things. The simplest way to do this, would be to create, say, 10000 tasklets and measure the process' memory footprint before and after. K
> -----Original Message----- > From: stackless-boun...@stackless.com [mailto:stackless- > boun...@stackless.com] On Behalf Of Andrew Francis > Sent: 9. október 2009 19:38 > To: stackless@stackless.com > Subject: [Stackless] Size of a Tasklet > > Hi Folks: > > I have read that a tasklet's overhead is roughly 400 bytes. > Using Stackless 2.6.2 3.1b, I use the sys.getsizeof() on tasklet. I get > 56 bytes. I directly call the __sizeof__() and get 44. Can anyone > explain these numbers. Again, I am putting the finishing touches on my > slides and I want to clarify things. > > Cheers, > Andrew > > > > > _______________________________________________ > Stackless mailing list > Stackless@stackless.com > http://www.stackless.com/mailman/listinfo/stackless _______________________________________________ Stackless mailing list Stackless@stackless.com http://www.stackless.com/mailman/listinfo/stackless