View Single Post
Old 08-02-2011, 03:40 PM   #23
pruss
Evangelist
pruss ought to be getting tired of karma fortunes by now.pruss ought to be getting tired of karma fortunes by now.pruss ought to be getting tired of karma fortunes by now.pruss ought to be getting tired of karma fortunes by now.pruss ought to be getting tired of karma fortunes by now.pruss ought to be getting tired of karma fortunes by now.pruss ought to be getting tired of karma fortunes by now.pruss ought to be getting tired of karma fortunes by now.pruss ought to be getting tired of karma fortunes by now.pruss ought to be getting tired of karma fortunes by now.pruss ought to be getting tired of karma fortunes by now.
 
Posts: 461
Karma: 819417
Join Date: Nov 2004
What you describe is much worse performance than what I see on my A43. I had no idea it was THIS slow. In none of my testing is it this slow. Refreshing a single page on my A43 takes at most a second, and with render-ahead enabled, the next page is always waiting for me.

I think I know what the problem is. The problem is that not enough memory has been allocated for the render-ahead option to work on a screen resolution as high as yours. For your screen, we'd need to allocate at least 5mb, maybe as much as 6mb, while we are only allocating 4mb.

To test this hypothesis, could you try switching APV's color rendering mode to "Normal black and white"? This will reduce memory usage by half, hopefully fitting everything into the internal cache. Then see what performance is like.

If it turns out that the cache memory is the issue, I can increase the cache to 6mb, and then have a 4mb fall-back in low memory conditions.
pruss is offline   Reply With Quote