>Although we see it calls the growing time write_log function first, so that may be the main reason. I can comment out this function and re-test, but I think I identified the main culprit for slowness is write_log function.
>
>I look up this procedure and it stores every message in the property, so this property is going to grow more and more and therefore the execution time is going to slow down.
>
Yuck.
Going against the basic assumptions of logging in computerverse and having the problems we deducted...

>I'm not sure what can I do to not let it grow that much. Although I found one potential thing to make it run quicker and implemented it.

Hope that you did NOT take the route to StringToFile as an alternative,
instead implemented a logobject resposible for some LLF-streams.
Bonus shoulder pats if you already went with scripting or another way to skip the 2G barrier.