J
jonathan.wilson
Guest
We have the same issue with our Webspeed and larger reports. The Devs love TEMP-TABLES but our agents always end up in a mess memory wise. On the surface the code looks good. Our work around is just to use: wtbman -name MyWebBorker -refresh "refresh" is easier then trim/add can be done online (we use stateless); it just waits till the agent becomes AVAILABLE then kills/readds it back into the pool. Give us back lots of memory, once a day is enough for our Ops system. But we could do it more often. We also do it with our AppServer (classic).
Continue reading...
Continue reading...