best way to reduse memory usage of my script ?

[dzlee]

hello autoit developers community
i have some question , i hope to find the answers of it :
- in large project or even in small ones
how to make my compiled script use less memory ?
- how to test my script and be sure that there is no memory leak , or whatsoever reduce my script performance ?
- where can i find anything talks about autoit script architecture to avoid bad script design ?

last thing i find these script
can anyone describe how these scripts work and is these script actually work fine
thanks

Func _ReduceMemory()
    Local $ai_GetCurrentProcessId = DllCall('kernel32.dll', 'int', 'GetCurrentProcessId')
    Local $ai_Handle = DllCall("kernel32.dll", 'int', 'OpenProcess', 'int', 0x1f0fff, 'int', False, 'int', $ai_GetCurrentProcessId[0])
    Local $ai_Return = DllCall("psapi.dll", 'int', 'EmptyWorkingSet', 'long', $ai_Handle[0])
    DllCall('kernel32.dll', 'int', 'CloseHandle', 'int', $ai_Handle[0])
    Return $ai_Return[0]
EndFunc

Func _SelfReduceMemory()
     DllCall("psapi.dll", "int", "EmptyWorkingSet", "long", -1)
EndFunc

 

Edited June 20, 2015 by dzlee

[water]

- where can i find anything talks about autoit script architecture to avoid bad script design ?

The wiki has a section about good coding practices.

[dzlee]

The wiki has a section about good coding practices

i am really grateful to you
i take a look on it ,it's very helpful
thanks again bro

[water]

Glad to be of service
We could even be more helpful if you could post your script.

[dzlee]

i'm about to start in storage management project
which i think will be a large script
connected to sqlite database
and, the script will run on windows xp with 512MB ram
so i am concerned in script performance
that's what i asked these question

Edited June 20, 2015 by dzlee

[jchd]

Develop your application first, keeping in mind to use large variables wisely w.r.t. their lifetime. Use the power of SQLite internally instead of using AutoIt code to process large, raw output. The actual size of the .au3 code is almost irrelevant and you can always use stripping to remove unused parts from the runable code. Then only check if the result requires too much, search where the issue is and workout a way to decrease memory size for this part.

The functions posted in the OP are not going to really help you, and possibly bite you someday.

[dzlee]

i will try to do exactly what you say
thank you for advice

[TheSpannish]

I think that if some parts of your script you add sleep() it wont use so much memory, the inconvenience its that it will take more time to load... If you are planning to use another program here I have a script that will reduce the memory of the program you say  (its same as yours but you can select the program)

Func _ProcessReduceMemory($iPID)
        Local $iProcExists = ProcessExists($iPID)
        If Not $iProcExists Then Return SetError(1, 0, 0)
        If IsString($iPID) Then $iPID = $iProcExists
        Local $hOpenProc, $aResult
        $hOpenProc = DllCall("Kernel32.dll", "int", "OpenProcess", "int", 0x1F0FFF, "int", False, "int", $iPID)
        $aResult = DllCall("Kernel32.dll", "int", "SetProcessWorkingSetSize", "hwnd", $hOpenProc[0], "int", -1, "int", -1)
        DllCall("Kernel32.dll", "int", "CloseHandle", "int", $hOpenProc[0])
        If Not IsArray($aResult) Or $aResult[0] = 0 Then Return SetError(2, 0, 0)
        Return $aResult[0]
EndFunc   ;==>_ProcessReduceMemory

 

[water]

I think the best approach is to avoid memory leaks. Means: Release storage when it is no longer used.
Set unused arrays to "" to release the memory, set unused objects to 0 to drop a connection, application or whatever.

[TheDcoder]

Also keep in mind that empty arrays take space too... Also develop a specific kind of programming pattern in your program if you are making a huge program, note that you don't have to plan your programming pattern first-hand, you will have to do it when you start coding your script, that ways its much easier. These are things which I follow when I code a big code hungry script.

 

TD

[Jos]

Also keep in mind that empty arrays take space too... Also develop a specific kind of programming pattern in your program if you are making a huge program, note that you don't have to plan your programming pattern first-hand, you will have to do it when you start coding your script, that ways its much easier. These are things which I follow when I code a big code hungry script.

  This is as clear as mud to me but am sure there is some logic somewhere.

[water]

note that you don't have to plan your programming pattern first-hand, you will have to do it when you start coding your script, that ways its much easier.

I would like to see one of your huge scripts made with this principles in mind. All we have seen until now are some small and simple scripts

When trying to make good scripts/programs it is not about coding but planning. The design you make before you write the first line of code is what makes good code or in absence you get a pile of s..t sooner or later.
Coding is less then 10% of the effort to write a good program. The rest is design, testing, documentation etc

Just my 2 cents..

[dzlee]

i understand it now
performance about code design ,release resource ,use variables wisely ,make sqlite do the work for you ..
thank you guys
[solved]

[TheDcoder]

@Jos That way its much easier for you to start coding soon (earlier?)

@water You are not going to see a huge script made by me anytime soon!

 

TD

[water]

TheDcoder,

Do you start driving before you know where you want to go to?
First comes planning, then comes doing. Wikipedia describes it much better: PDCA.
Happy reading
 

[BrewManNH]

In reference to the 2 scripts posted in this thread so far, neither one of them will actually reduce memory usage of your script. What both of them do is to take the memory that your program is using and dumping it to disk in the page file. In other words, it will reduce the RAM being used, but the data that was in the RAM is now in your page file, and being disk based it will make your program run much slower if if needs any of that information that on the disk. It's a band-aid on a bullet wound, you should try and fix any memory issues with your script before you resort to ruining its performance this way.

In Windows XP memory management was terrible, so this type of script had limited usage. In today's modern OSs this is totally unnecessary because Windows handles the memory management and your scripts shouldn't try to do it. Microsoft is a lot smarter about memory management than you or I. Memory is usually plentiful, and much faster than disks, leave the data there and let Windows decide when it should page it out.