03-16-2018, 10:57 PM
looks like all the table entries made, just that last one failed... I see how the updates and logs table work now, made for quick double check what was applied.
just a thought, if an update is going to make my webhost crap its pants with maxed out memory and 100{3bc1fe685386cc4c3ab89a3f76566d8931e181ad17f08aed9ad73b30bf28114d}cpu, to then timeout... could it be segmented maybe? click update, response, garbage collection, click next update...respomse, garbage collection, etc... I guess I am assuming that all the array data is to blame for heavy ram usage... hmm, i could be wrong though. At the moment im just glad i didnt have to blow the DB away and start with this version 4.3.16's fresh new db smell.
8 -)
Bradely
just a thought, if an update is going to make my webhost crap its pants with maxed out memory and 100{3bc1fe685386cc4c3ab89a3f76566d8931e181ad17f08aed9ad73b30bf28114d}cpu, to then timeout... could it be segmented maybe? click update, response, garbage collection, click next update...respomse, garbage collection, etc... I guess I am assuming that all the array data is to blame for heavy ram usage... hmm, i could be wrong though. At the moment im just glad i didnt have to blow the DB away and start with this version 4.3.16's fresh new db smell.
8 -)
Bradely