On Sun, 14 May 2000 [EMAIL PROTECTED] wrote: > That graphics card is a 2d card, which requires rendering to be in > software. That system supports a mid-range 3d accelerator, GXT3000P. > Hardware rendering in DX will take advantage of the OpenGL support in that > card.
I am surprised to hear you call GXT3000P a "mid-range"! Can I call GXT2000P a "mid-range"? > Your workstation will support a 2nd processor, if you don't have one > already. Computational operations in DX can run in parallel with the two > processors. I didn't know this... Thank you to let me know! > Since your dataset is not that big, my guess without seeing > any further information, is to get the hardware accelerator. > You mean that the bottle neck, if exists after I correct the setting you suggested in other mail, should be graphic card or cpu? I hope tweaking system configuration magically improve the performance. Wish me a luck. Thank you again. yosuke kimura > > yosuke kimura <[EMAIL PROTECTED]>@opendx.watson.ibm.com on > 05/12/2000 07:09:09 PM > > Please respond to [email protected] > > Sent by: [EMAIL PROTECTED] > > > To: [email protected] > cc: > Subject: [opendx-users] Where to spend money to make it faster? > > > > > Dear list members, > > I'd appreciate if you can share some experience with dx. > > We have IBM's RS/6000 43P Model 260 with 256MB RAM. We use data explorer > to <100 * <100 * <20 rectangular gridded scaler/2d-vector data. We use > 3-D isopleths the most. Our problem is that when we use dx interactively, > rendering takes long time. So we want to figure out where to spend money > to let the system respond more quickly. > > Our system has 256MB, and graphic card is POWER GXT120P (or 240?) Graphics > Adapter. We have OpenGL (is this a library or a hardware?), and OS is AIX > 4.3. > > -- > yosuke kimura > Center for Energy and Environmental Resources > The Univ. of Texas at Austin, USA > > > > -- yosuke kimura Center for Energy and Environmental Resources The Univ. of Texas at Austin, USA
