I ran my tests again, only with antialiasing disabled this time (for font sizes between 6 and 14). The results of the first run are repeated here, and dillo2n represents the new runs. Please refer to my previous email for a detailed description of the tests. I also experimented with sub-pixel rendering, without antialiasing (dillo2ns) and with antialiasing (dillo2s) First run: ---------- Results: time1 time2 delta/30 prps mem(KB) dillo1 1.36s 1.82s 15ms 67 2516 dillo2 3.10s 6.90s 126ms 8 3624 dillo2s 3.23s 7.16s 131ms 7.6 n/a dillo2n 3.34s 5.33s 66ms 15 3628 dillo2ns 3.16s 4.94s 59ms 17 n/a Conclusion: While disabling antialiasing rendering doesn't seem to change anything for the start time (which was already acceptable, IMHO), it doubles the speed when scrooling entire pages! With this setting, dillo2n became useable. Not quite as snappy as dillo1 (still 4 times slower on redraws), but very acceptable. Turning off antialiasing doesn't change the amount memory used. Turning on sub-pixel rendering doesn't affect the rendering time, but seems to improve the quality only when used with antialiasing. However, my fonts look ugly with gtk-2.0 and I don't seem to be able to find any setting that helps (it seems to scale non-scalable fonts). With gtk-1.2, the font look good. Second run: skipped. Third run: ---------- This is a scaled down version of the second run. I took the same file and kept only the first 2000 line. The test file is 684 KB. Results: time1 time2 mem(KB) dillo1 5.1s 35s 12708 dillo2 31.5s 2m53s 33520 dillo2n 29.9s n/a 33652 Conclusion: Nothing changed here: loading big pages is still painful brings the whole machine down on its knees when swapping starts. For the record, the real time (time2) was 2m10s, but the load on my system was completely different today, so I don't this it compares to yesterdays results. Fourth run: skipped. Fifth run: ---------- This is a free run of internet browsing, to get an overall feeling. No numbers for this one. Includes browsing several sites, open up to 8 windows, switch between them and close them all, click on the floppy disk to save URL. Selecting text was fast. Conclusion: Still feels heavy. Faster on scrolling, acceptable, in fact, but any operation is still taking enough time for me to notice I'm actually waiting for the redraws to occur. Particularly when overlapping redraws occur (X Expose events), like switching from one window to another. Also, as another poster noticed, *closing* windows takes a significant amount of time (this is certainly related to freeing much more memory than dillo1). I timed another operation to give you an idea: I opened and closed (cancel) the save URL dialog 5 times in dillo2n, substracted the start and closing time as usual and divided by 5: 1.4s each time (user time, real time more like 6s). Same experience with dillo1: 0.09s. Now that's what I'm talking about! (could not get any real time, most of it is spent by moving the mouse from one button to another) Final conclusion: ----------------- If we go with gtk-2.0, we absolutely need to document this antialiasing setting: I had a hard time finding that some information was on fontconfig.org! If we also can point to font de-uglyfication of gtk-2.0, that would help a lot. Regardless, like Stephen said, memory usage is a huge problem. I assume this cause by the libraries and the implementation in dillo is the same (i.e: dillo's structure did not grow x2.5 because the the port). Until this problem is solved, I don't think gtk-2.0 is a viable option for dillo. Disabling antialiasing definitely solves most of my concerns about speed: if only I could get the font to be as clean as gtk-1.2, I would be happy. Best, EG PS: the patch is still alpha-quality and has a lot of rendering bugs: font-factor screws-up positionning, text selection hightlights at the wrong place, etc.