Hello Simon, Both raid controllers are brand new and working with cache.
We use RedHat AS3 and when looking with the dset utility, the DELL server transferes aprox 35M/s read and write from/to the disk when restoring The HP does aprox 10k/s read/write!! When building the data volumes both servers worked fine. Both servers use 8G of memory. How can the CPU get involved in this? the CPU is completely bounced (95-100% I/O wait). Regards, Bart Lubberdink Hello, > > We use sapdb 7.4.3.31-1 on two different servers. > One server is a Dell PowerEdge 6850 and the other is a HP Proliant DL580 > G3. > When checking both systems, the dell is a little bit faster when writing > to disk and reading from disk but this is normal because the Dell has 256M > cach on the raid controller and the HP 'only' 192M. > When i create a database from a backup, both machines create the log and > data volume almost in the same time (normal write speed) > There is one Log volume from 5G and 3 data volumes of 25G. > This takes about 40 minutes to build. > The problem begins when the actual data is imported form the backup to the > database. > The Dell server completes the restore (42G) in 40 minutes but the HP is so > very slow that after 3 hours, just 1G is imported! > > Is there a problem with the compatability between sapdb and the HP > controller "Smart Array 6i"? > Or does anyone have a clue what can be the problem here? There is much more involved than the RAID controller here. CPU, RAM, OS, almost everything. However, if you want to concentrate on the RAID controller, have a closer look at the cache. Do they both have battery backed cache, and are the batteries in good condition. Usually only then the cache is operated in write-back mode. Simon > > Regards, > > Bart Lubberdink > RAM Mobile Data > > -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
