Linux Today: Linux News On Internet Time.
Search Linux Today
search.internet.com
Linux News Sections:  Blog -  Developer -  High Performance -  Infrastructure -  IT Management -  Security -  Storage -
Linux Today Navigation
LT Home
Preferences
Contribute
Link to Us
Search
Linux Jobs

Become a Marketplace Partner

internet.commerce
Be a Commerce Partner














The Linux Channel at internet.com
Linux Today
Enterprise Linux Today
Apache Today
JustLinux.com
Linux Planet
PHPBuilder
All Linux Devices
Technology Jobs

JustTechJobs.com

LinuxToday Newsletters
Subscribe News
Subscribe PR
Subscribe Security

internet.com
IT
Developer
Internet News
Small Business
Personal Technology

Search internet.com
Advertise
Corporate Info
Newsletters
Tech Jobs
E-mail Offers

 






Current Newswire:

Installing Ubuntu 9.10

Hands-on: OpenMoko WikiReader is simple, appealing

Perl far from dead, more popular than you think

Microsoft Exchange alternatives

Kubuntu 9.10: A Mixed Bag

Could Microsoft switch to Linux?

Red Hat Virtualization Manager for Windows Only?

Creating Ebooks with Sigil

Editor's Note: Making Multi-Channel Firewire Music With Linux

Amaya: A Simple, Yet Useful Alternative to Dreamweaver




Server Support Specialist I
The Computer Merchant, Ltd
US-OK-Oklahoma City

Justtechjobs.com Post A Job | Post A Resume
:MySQL: Five More Dials To Turn
MySQL: Five More Dials To Turn
Jul 9, 2009, 16 :33 UTC (0 Talkback[s]) (1866 reads)

(Other stories by Sean Hull)

"6. Innodb
InnoDB is likely your storage engine of choice for MySQL as it provides transactional support, as well as crash protection.

innodb_buffer_pool_size

"Typically the InnoDB buffer cache should get the bulk of memory on the system. So for example if you are just running MySQL on your server (we hope so), then perhaps 20% of the memory can go to the OS, 20-30% to sessions, and the remaining 50% to static buffers in MySQL. If you're not using MyISAM most of that 50% will be for this InnoDB buffer pool.

calculate innodb buffer pool hit ratio
1 - (innodb_buffer_pool_reads / innodb_buffer_pool_read_requests)

"A hit ratio is not a bulletproof way to tune I/O, but it can give you a good indication and starting point from which to tune. Since InnoDB caches both data and index in this buffer pool, the hit ratio here will tell you overall the % of hits that are satisfied by going to memory versus the ones which require disk I/O. You want to do as little disk I/O as possible, so a higher hit rate here means you're caching better and more relevant blocks to your applications needs."

Complete Story

Related Stories:
Interview with Daniel Chalef of KnowledgeTree(Jul 09, 2009)
Five Places You Can Slash IT Spending(Jul 09, 2009)
PostgreSQL 8.4 Improves Database Management, Security(Jul 02, 2009)
The New MySQL Server Release Model(Jun 30, 2009)
EnterpriseDB Brings Postgres Closer to Oracle(Jun 18, 2009)
Drizzle: Rethinking the MySQL Database Kernel(Jun 16, 2009)
MySQL: Five Dials to Set(Jun 12, 2009)



No talkbacks posted.
  Home | Search Talkbacks | Customize View    Top of Page  



Enter your comments below:

* Your Name:

* Your Email Address:

* Subject:

CC: [will also send this talkback to an E-Mail address]

* Comments:

Tags allowed:<I>,<B> and <U>. See our talkback-policy for more about talkback content.

Fields marked with * are required!






..............................




All times are recorded in UTC.
Linux is a trademark of Linus Torvalds.
Powered by Linux, Apache and PHP

internet.commediabistro.comJusttechjobs.comGraphics.com

Search:

WebMediaBrands Corporate Info

Legal Notices, Licensing, Reprints, Permissions, Privacy Policy.
Advertise | Newsletters | Shopping | E-mail Offers | Freelance Jobs