The database and the forum software itself is optimized to keep the most active topics cached and in an easy to access manner. Writing threads is an extremely expensive process compared to reading, especially as topics tend to age and things get disorganized. The database stores individual posts and then a list of threads the posts belong to, and when it updates a thread it has to read each of these individual posts and assemble a thread with it.
When you bump an old thread like that, you end up pulling a bunch of posts that were otherwise dormant and archived back into an active state. The forum software is going to grab all the posts from that thread and cache them under the expectation that they may get accessed again, when likely they won't. Reads don't do this (except on the very first time a thread is read) because the final output was already made and since it hasn't changed it can just reuse that. This is why when you post it seems to take a long time, yet clicking on a thread and just reading doesn't. Little data is actually sent (text is ridiculously small bandwidth wise), it's the time spent having to rebuild the thread view that takes a while.
It's better to just make a new thread, and link to the old one if you have something relevant to add. Only bumps we allow are status update bumps from the OP for things like project threads.