I am wondering if this will affect our VR application. We use pointers to DX data inside draw operations that occur on multiple graphics heads so memory locks may be important even in DX's single-processor mode. Our project is going slowly, so it's too soon to tell, but I'll keep a mental note of this. When you code it, please provide a mechanism to turn it back on if needed, either a compile option or environment variable would be ok.
Thanks Richard Gillilan Cornell Theory Center Randall Hopper wrote: > From profiling dxexec, I've found that 20-25% of it's time in the > single-process case is spent locking and unlocking mutex locks (on SGI). > AFAICT these locks add unnecessary, avoidable overhead to the > single-process case. > > I can cook a patch so that mutex locks are only used in dxexec when > "nprocs > 1". But before I do, I'd like to find out whether the DX > committers would be willing to commit this patch. > > Greg? David? > > Thanks, > > -- > Randall Hopper (mailto:[EMAIL PROTECTED]) > EPA Scientific Visualization Center > US EPA MD/24 ERC-1A; RTP, NC 27711
