It's mostly loading the rows from talktext2 though, since that's potentially a LOT of data off of the disks. If you have 250 comments on the page, all reasonably long (couple kilobytes), you're talking about loading a megabyte of data...
Which is a lot. But, caching! You might mention caching! That should fix this problem, right?
Well, sure, to some extent. There's a compounding problem in popular communities where people are editing and posting new comments a lot, leading to some of the caches getting cleared fairly often.
Of course, counter-argument is: computers have gotten a lot faster since this was instituted a few years ago. We now have so much RAM available that we can, in theory, maintain huge cache hit rates and maybe give people everything they want and a bunny rabbit...
But I dunno. We'll have to play with it over time. I'll be gone for the next month, but I'm amenable to revisiting old LJ performance decisions to see if we can get around them.
no subject
It's mostly loading the rows from talktext2 though, since that's potentially a LOT of data off of the disks. If you have 250 comments on the page, all reasonably long (couple kilobytes), you're talking about loading a megabyte of data...
Which is a lot. But, caching! You might mention caching! That should fix this problem, right?
Well, sure, to some extent. There's a compounding problem in popular communities where people are editing and posting new comments a lot, leading to some of the caches getting cleared fairly often.
Of course, counter-argument is: computers have gotten a lot faster since this was instituted a few years ago. We now have so much RAM available that we can, in theory, maintain huge cache hit rates and maybe give people everything they want and a bunny rabbit...
But I dunno. We'll have to play with it over time. I'll be gone for the next month, but I'm amenable to revisiting old LJ performance decisions to see if we can get around them.