[...] > And even if I had enough RAM to keep only 6 GB: At the > current read-spead of the DB it takes almost 2 hours to > completely slurp in the data. > > Working with this system you can actually feel this: If you > access something by an index that is currently not cached it > takes _ages_ - subsequent accesses are as quick as you would expect. > > I'd like to hear something from SAP here: What kind of > hardware do they suggest for proper i/o-performance?
We are seeing this too - and IMHO it's not the I/O subsystem that is causing issues but the sequential read of the database itself (no PQO, no prefetch (yet)). We're actually seeing this when we're exporting a (SAP) database of ~ 150 GB. It takes about 28 hours to determin the size of the tables (via select count(*) <tablename>) - over the weekend on a not loaded EVA system. The parallel export itself is then done in 4 hours. This issue is known and AFAIK beeing worked on. Greetz, SIEGENIA-AUBI KG Informationswesen i.A. Markus Döhr SAP-CC/BC, SAPDB-DBA Tel.: +49 6503 917-152 Fax: +49 6503 917-7152 E-Mail: [EMAIL PROTECTED] Internet: http://www.siegenia-aubi.com -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
