On Thu, Apr 10, 2008 at 06:46:46PM +0100, pedro mg wrote: > Still, talking about images, for Twittershoes case, looking at the > meta 'etag' forces a pull from all the images, all the times. So we > get that delay.
Ohhh, you're absolutely right. Okay, I'll get right on this. > I was trying to find the source code where you refer you keep a single > reference to each unique loaded image. Is it ruby coded ? No, it's in shoes/image.c. The st_lookup and st_insert lines. I'm using Ruby symbol table hashes to store them. > One other thing, are you reading 16K chunks of data on the possibility > of huge images ? Yes. To avoid blocking threads and to avoid allocating more memory than I have to. _why
