jesperbrannmark wrote:Oh thats nice.
Suggestion:
Logging!! (like if I run a program for a long time so save to a csv file every minute CPU and mem average)
OK, it now has an option to log the average cpu and memory usage by the minute. The file is saved as "PureMonitorLog.txt" in your "Documents" folder. Use the same download link as from above.
Fixed a division bug and added a MessageRequester(). If you are logging your resources and you close your app, a MessageRequester() will pop up and ask if you want to open the "PureMonitorLog.txt" file. Use the same download link as from above.
J. Baker wrote:Are you talking about a threshold for memory?
It could be but it also could be cpu usage.
You could for example decide that you don't want the cpu load to get above 25%.
If you would give some kind alarm when it crosses that (could be a sound or show the max cpu load in the application badge for a few seconds), you know what parts of your application need improvement.
J. Baker wrote:Are you talking about a threshold for memory?
It could be but it also could be cpu usage.
You could for example decide that you don't want the cpu load to get above 25%.
If you would give some kind alarm when it crosses that (could be a sound or show the max cpu load in the application badge for a few seconds), you know what parts of your application need improvement.
Yes, that does sound good. I had been thinking memory but one for the cpu would be good too.
What I was thinking about memory, is that if the memory keeps going up and up, there may be a memory leak. Then the app would give a warning. I guess I could do that for both the cpu and memory. Looks like we are thinking on the same page.
Now what I wasn't sure about is... What if the user walks away from their computer and it throws a warning on one of the two. Should I set a timer, that if the warning isn't responded to, it kills the app?
Nice ideas but I hope someone wouldn't walk away too far when testing there app out. By that, I mean having to send an email. I don't know though, I could be wrong.
J. Baker wrote:What if the user walks away from their computer and it throws a warning on one of the two. Should I set a timer, that if the warning isn't responded to, it kills the app?
I would only kill an app automatically if the available free memory (can also be checked) gets too low.
J. Baker wrote:What if the user walks away from their computer and it throws a warning on one of the two. Should I set a timer, that if the warning isn't responded to, it kills the app?
I would only kill an app automatically if the available free memory (can also be checked) gets too low.
Yes, that would be best. I will definitely look into it thoroughly before making any final decision on that option.