Sounds like a memory leak caused by the database connection. The solution is simple: Set the database job to run detached. After that if you have time you can make it even more efficient by redesigning the job. Instead of having a job connecting/disconnecting to db every minute change it to a job that starts one connects to db and then every minute runs the same query never leaving the loop. Example: DatabaseConnect "my profile"
LoopWhile True, END_LOOP
DatabaseRetrieve ...
If .. check results
Wait 60
END_LOOP: : Wondering if you can help. : We have 24x7 running. Our server is rebooted once per weak. : When 24x7 first loads it is about 13MB. Through the week this grows to
: ~250MB. : There is a job which runs once every minute which checks a database and fires
: a second job if required. It would only fire a second job 1-6 times per
: day. Is there any rerason for this increasing memory usage...are there
: anythings we can put into place to stop it? Anything to look for in the
: job running once a minute which wouold cause this memory increase? : Let me know if you require more information. : Regards : Matt
|
