Bad performance with DBSPACETMP enabled

I'm currently using OnLine 7.23 on a HP K460 server. I have one big table (appr. 1 GB) for which we do an "UPDATE STATISTICS HIGH" on a regular basis. When using 3 temporary dbspaces on raw devices, the running time for this task is about 2 hours. If I dont't use temporary dbspaces, so that every temporary object is placed in the UNIX file system /tmp, the execution time drops down to 50 minutes. Anybody having any ideas about the reason for this bad performance, which also occurs when creating indexes. Should I use temporary dbspaces on raw devices at all or let OnLine better use /tmp ??? Thank in advance Rainer von Bongartz -----== Posted via Deja News, The Leader in Internet Discussion ==----- http://www.dejanews.com/ Now offering spam-free web-based newsreading