2006/2/16, Henrik Hempelmann <[EMAIL PROTECTED]>: > > Just wanted to make sure I didn't miss anything: this refers only to > > the COUNT(*) issue, does it? Are there any other IO speed related > > optimizations that make performance behavior differ significantly > > between 7.5 and 7.6 (even if only for certain usage scenarios)? Thx! > > Yes, :-) > we are currently working on speeding up the read i/o performance. > It will be possible to assign larger tables with few changing records > to a continous clustered storage area. This allows us to read larger > chunks of data in one i/o call, which actually improves read > performance. > ... this will happen in a upcomming 7.6 release.
Ah! That's interesting to hear. So basically there will be some command that nails down a single table to a volume and prevents scattering of data across multiple volumes. Did I get that right? Is there also some form of automation (i.e. MaxDB detects tables that are eligible for this and does it automatically)? Sorry for being so curious. :-) Kind regards robert -- Have a look: http://www.flickr.com/photos/fussel-foto/ -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
