Henrik Hempelmann wrote: > Falk Br�gmann wrote: ... > > The problem is, we are not quite happy with the performance of our setup > > yet. When a not-too-high number of users tries to access the > > application, the database comes under load pretty quickly (as measured > > by the Unix "top" command), and normally fast queries start to take several seconds. > > load (average:) of the run queue or load (user%) of the CPUs?
Load average of the run queue; the user% load is not tracked by our monitoring tool, but as far as I know, the user% load of the CPUs is not critical. > > Our current configuration parameters are: > > . CACHE_SIZE = 100000 > -> 800MB Cache, you should double the chache size on a 2GB machine > > > The data and log volumes are plain files (not raw devices) sitting on an > > ext3 (journaled) file system. > assure data journals on ext3 are disabled We'll do both of that. Thanks for your quick and helpful response! =) Falk -- NEU : GMX Internet.FreeDSL Ab sofort DSL-Tarif ohne Grundgeb�hr: http://www.gmx.net/info -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
