Peter;177773 Wrote: > Just so you know, 18.000 records is *nothing* for MySQL. Yes that is true. As long as you don't memory starve it. Otherwise you'll put the HD speed in the equation...
My DB data file is about 240MB, yet SlimServer comes with MySQL configured to the default innodb_buffer_pool_size, an that is 16MB. Guess what happens... >From the MySQL reference manual: > innodb_buffer_pool_size > > The size in bytes of the memory buffer InnoDB uses to cache data and > indexes of its tables. The larger you set this value, the less disk I/O > is needed to access data in tables. On a dedicated database server, you > may set this to up to 80% of the machine physical memory size. However, > do not set it too large because competition for physical memory might > cause paging in the operating system. So setting it to 64MB seems reasonable for larger collections on a machine with 1GB RAM. Regards. -- Raptus ------------------------------------------------------------------------ Raptus's Profile: http://forums.slimdevices.com/member.php?userid=1852 View this thread: http://forums.slimdevices.com/showthread.php?t=32417 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
