It never even occurred to me that someone would do this and not see the problem with it.
Exactly, I do not see any problems with it because the tool itself is working well (with exception to iwiki spy, which indeed can be improved with use of another suggestions collection algorithm).
You now have two options: you can continue to discuss this on the mailing list, which will not result in the limit being removed[0], or you can look at a way to perform the same result without needing such large MEMORY tables. I would suggest that the latter is a more productive use of your time.
I guess it is not possible to reduce the limit in the bot and keep bot's performance at least on the same level at the same time. You know administration well, I know the application domain of connectivity analysis.
I really think that the only acceptable solution for golem to continue working is to get the limit removed. No matter if this will be achieved with additional memory installed to servers or any other way. This does not mean of course I should not think about memory usage, and I will like I was in the past if the bot will be allowed to work. Not now.
I believe you also have even more than just two options. To keep the limit at cassia, or to remove it. You also can introduce similar limit on thyme and daphna. Why not? In your options list for me I do not see any, which allows you helping golem to run again as a toolserver administrator.
mashiah