after stopping the load of the db, the db people deleted all the data from the table, and then, while they do that the utilization of the THREE dasd's was about 60% each.
what could causing the system to utilize the dasd's at 10% while loading the data, and 60% when deleting? i really dont understand it :-( thanks On Thu, 27 Nov 2003, Rob van der Heij wrote: > On Wed, 2003-11-26 at 21:30, Alejandro Leyva Rabinovich wrote: > > > i know that the message "I/O RATE LIMIT EXCEEDED: INFRAC01 643 SEC" > > reffers to a treshold that rtm have, but, does it have any relationship > > with cp? does z/vm do something when a user exceed the i/o rate limit? > > No, the observation that RTM makes does not go back to CP. It is only > meant to alert (automated) operators who call you in the middle of the > night about this (or about storage utilization > 100% ...) Other than > that there is no reason to adjust the threshold. > > You could however set a throttle on the device to make CP limit your I/O > rate on the device if you wish. > > PS I guess the rate of 600 I/O's per second is pretty high and I would > expect very small channel programs. With the lazy write in Linux one > would expect filling a database to result in long channel programs > writing a lot of blocks at once. Maybe you already saturated memory and > bdflushd is running constantly. > > Rob > -- Alejandro Leyva Rabinovich. Jefe de la Unidad Departamental de Soporte Ticnico (Administracisn de Mainframe). Direccisn General de Informatica. Secretarma de Finanzas. Gobierno del Distrito Federal.
