RE: Witango-Talk: itembuffersize

[Robert Shubert]

My advice is to try it and see. Most DBs use 4k or 8k as their largest row size (excluding col types of TEXT, BINARY, etc).   Witango will allocate a chuck of memory this size in preparation of data incoming from the datasource, it’s possible to see a slight improvement, especially in memory management with a smaller number. Don’t get your stop watch out, though, any change would likely be noticeable only in thousandths of second, and then only on very large result sets.   I’d be interested in anything you find.   Robert   -----Original Message----- From: Alan Wolfe [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 27, 2004 3:26 PM To: [EMAIL PROTECTED] Subject: Witango-Talk: itembuffersize   from the help it says this setting is...   Specifies the size, in bytes, of the largest column value that can be retrieved from a data source. You need to increase this value only if you need to retrieve large values. The default value is 65535 (64K).   probably the biggest column we ever retrieve from a DB is 500 bytes, leaving some breathing room, we could set this setting to 1 or 2k, but would there be any benefit for doing this?   we have our db on the same machine as witango if that makes a difference.   Thanks! Alan ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf