One installation of PS60 for each app -> Reduce memory consumption of PyS60 2nd ?

[cyke64]

Hello ,

I have an interesting question for you PyS60 guys

This question is only for 2nd edition : Is it possible to reduce memory consumption by installing Python libs (py , pyd files and python222.dll , python_appui.dll) in another location than !\system\libs for each standalone application ?
First Python is completely desintalled and for each application you must to re-install one version of Python by application in the folder of your standalone application !!!

???? = name of the standalone application
This guy install the libs in !\system\apps\????\libs
python dll in !\system\apps\????

So does it works ?
Cyke64

Here's the argumentation of this guy DJwa163 who pretends that it reduces memory consumption by 1.5 MegaByte when you are not using Python ...


Now you have the way out from spending about 1.5mb of RAM continuously for the Python lib files. This happens whether you use a Py app or not. But,s the memory consumption will remain continuous all through. And the same with the Battery life. constant RAM consumption will lead to rapid battery drainage.

Python libs, when placed in !/System/Libs,helps execute the Python dependent apps. These pyd libs create a platform (medium) where many Python apps are enabled to run, even simultaneously, many apps together.


Whether you Run a Python app or not, the pyd libs will continue to function on the background, keeping itself ready to launch and execute any python app at any point of time. Its absolutely not a need-dependent process. Its always hungrily ready to Run these apps, irrespective of you're ready to run that or not.

This is the reason why it keeps on draining RAM CONTINUOUSLY....

But, the same pyd files,when placed in someother directory, don't create a similar circumstance to Execute Any Python app. And its stops consuming the additional RAM.


And this property had inspired the idea of standalone. Though, it consumes enough from the memory card, the RAM is spared from getting robbed all the time.
But, in these standalone apps, the .py are compressed into .pyd and placed into the !/System/Apps/****/Libs folder, instead of !/System/Libs. These are only activated when you Run that particular standalone app. And, never run on the background, once you close the app. i.e. Its totally a need-based process.

But, the limitation is that one such
System/Apps/****/Libs directory and the pyd files are essential to run every such standalone app. And these are included inside these standalone.sis files. So, its basically an idea for RAM salvage at the cost of MMC space.

[y.a.k]

I don't think that's right. AFAIK the DLLs in Symbian are shared. If you're running several Python apps, they all share the same instance of the dll in RAM. When you close them all, the dll stays in RAM ready to serve another Python app. If you start one, the dll is already loaded into RAM ready to be used. However, if you don't start any Python app and some other app runs out of RAM, the unused dll will be removed from RAM to make space. Simmilar thing happends when you use the "compress RAM" option in apps like FExplorer (note that the name of this option is simply misleading).

[simo.salminen]

Yep, this is total BS.

[alb3530]

...Here's the argumentation of this guy DJwa163 who pretends that it reduces memory consumption by 1.5 MegaByte when you are not using Python ...


Now you have the way out from spending about 1.5mb of RAM continuously for the Python lib files. This happens whether you use a Py app or not. But,s the memory consumption will remain continuous all through. And the same with the Battery life. constant RAM consumption will lead to rapid battery drainage.

Python libs, when placed in !/System/Libs,helps execute the Python dependent apps. These pyd libs create a platform (medium) where many Python apps are enabled to run, even simultaneously, many apps together.


Whether you Run a Python app or not, the pyd libs will continue to function on the background, keeping itself ready to launch and execute any python app at any point of time. Its absolutely not a need-dependent process. Its always hungrily ready to Run these apps, irrespective of you're ready to run that or not.

This is the reason why it keeps on draining RAM CONTINUOUSLY....

The problem here is the main point of his technique isn't correct.

Python libraries are only loaded when Python is running.
When Python isn't in use, the libraries won't absolutely consume any amount of RAM

The only thing that will logically consume a little bit of RAM is the Python installer's recognizer, but it's a small amount of memory: some kbytes only.
Nothing to worry about


best regards