From: Brian P. <bri...@tu...> - 2006-08-18 20:32:28
|
Andres Lagar Cavilla wrote: > Hi again, > I've been reviewing an old thread regarding chromium performance and was > wondering what is the state of matters as of today, v1.9-rc4 > Assuming the network is not the limiting factor (big chunk of an > assumption, heh): > - Is chromium limited by CPU consumption during unpacking? I've seen > high rates of CPU occupation by crserver for several apps (quake 3, > mplayer, glxgears) It depends. If the graphics card is very fast, the limiting factor may be the unpacker/crserver, or it may be the network. One easy thing to do is run 'top' on the crserver host while Chromium's running to see how busy the CPU is. > - What about all the pointer swinging as function calls go down the > SPU's? If someone wanted to optimize a particular set-up, would it be > worthwhile replacing the spu loading mechanism with something less > general but potentially faster? I don't think function calls are too big of deal there; we're doing just about as good as we can. On Linux (and other platforms) we're using assembly code for dispatching GL functions (see opengl_stub/Linux_i386_exports.s). And if a SPU doesn't implement/override a particular GL function there's no undue cost. > - Anything else? With all the different possible Chromium configs, it's hard to be specific. Do you have a certain configuration in mind? -Brian |