[jitter] hardware questions

your biggest speed increase would probably come from uploading uyvy  
matrices as texture data, you would almost halve your bandwidth to the  
GPU (and potentially CPU processing as well), you could then use the  
cc.uyvy2rgba.jxs shader family to do YUV to RGBA conversion on the GPU.

Check the optimization threads about this technique. It works for  
movies, so it should work for arbitrary matrix data being treated as  
imagery on the GPU.

That machine is really fast, from what I can tell. I bet you would be  
better off optimizing your patch. jit.change, and asymmetric bangs to  
jit.gl.render vs metros to what your matrix/CPU land stuff is doing  
would help, along with qmetro/qlim magic, etc.

its hard to tell w/o a patch.

On Feb 1, 2008, at 11:44 AM, subzero wrote:

> Hello list,
> we are reconfiguring our WinXP PC at the moment to speed up the fps  
> in jitter. We use it basically to generate big matrixes (1920*1200)  
> and process these on the GPU.
> One of the bottle necks in this system seems to be loading the  
> matrix on the GPU as a texture. We did a lot of tweaking in jitter  
> to make this as efficient as possible. So the next step is to  
> upgrade the hardware, to speed up the fps.
> For this we have the following questions:
> What is the best choice of CPU? Is it more important to have the  
> fastest CPU's, the fastest CPU busspeed, or the size of the L2-cache?
> Regarding the motherboard, is the busspeed critical? And what about  
> the ammount and the speed of the memory?
>
> We currently use a 8800 GTX 768mb graphics card, with the Asus P5B  
> Deluxe wifi (busspeed 1066mhz, 4GB 667-DDR2), and a Core 2 Quad CPU  
> (Q6600 4 x 2400mhz, with a busspeed of 1066mhz and 8mb L2 cache)
>
> Hope some of you can shed some light on these matters,
>
> Best Lucas
>
>
> _______________________________________________
> jitter mailing list
> jitter at cycling74.com
> http://www.cycling74.com/mailman/listinfo/jitter