# innodb and HIGH server load

**URL:** <https://forums.percona.com/t/innodb-and-high-server-load/104>\
**Category:** Other MySQL® Questions\
**Created:** [October 20, 2006, 2:01pm UTC](https://forums.percona.com/t/innodb-and-high-server-load/104 "2006-10-20T14:01:15Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![spud](https://avatars.discourse-cdn.com/v4/letter/s/13edae/32.png) [@spud](https://forums.percona.com/u/spud)\
**Post date:** [October 20, 2006, 2:01pm UTC](https://forums.percona.com/t/innodb-and-high-server-load/104/1 "2006-10-20T14:01:15Z")

</div>

hi,  
i’ve some two forum tables with abot 700Mb each one, and they was type myisam. I was getting some lock problems and i decided to switch them to innodb, but server load growed from 3 to 20. I followed your steps but i got not any server load improvements.

should i back to myisam? or is there any way to solve it?

thanks

---

<div class="post-metadata">

**Author:** ![Peter](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/peter/32/2_2.png) [@Peter](https://forums.percona.com/u/Peter)\
**Post date:** [October 22, 2006, 5:54pm UTC](https://forums.percona.com/t/innodb-and-high-server-load/104/2 "2006-10-22T17:54:24Z")

</div>

spud,

Tuning server settings (I guess this is what you’re speaking about by following my steps) only helps if they are the main thing limiting your performance. In your case it might be something else. Going to Innodb tables should not be taken lightly - it may increase database size dramatically especially if you have a lot of indexes as Innodb does not pack indexes.

Also explain plans may change.

In your case I would take a look at queries and see which of them started to take a lot of time and then learn why it happened.

---

<div class="post-metadata">

**Author:** ![Speeple](https://avatars.discourse-cdn.com/v4/letter/s/73ab20/32.png) [@Speeple](https://forums.percona.com/u/Speeple)\
**Post date:** [October 23, 2006, 4:58am UTC](https://forums.percona.com/t/innodb-and-high-server-load/104/3 "2006-10-23T04:58:04Z")

</div>

Peter,

Is it true InnoDB doesn’t support packed keys even when specified?

E.g.  
ENGINE=InnoDB DEFAULT CHARSET=utf8 MAX\_ROWS=4294967295 PACK\_KEYS=1;

Will this result in packed keys or will it be ignored because of the storage engine?

---

<div class="post-metadata">

**Author:** ![Peter](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/peter/32/2_2.png) [@Peter](https://forums.percona.com/u/Peter)\
**Post date:** [October 23, 2006, 6:47am UTC](https://forums.percona.com/t/innodb-and-high-server-load/104/4 "2006-10-23T06:47:52Z")

</div>

Yes. Innodb does not support packet keys.

If you specify pack\_keys=1 it will be simply ignored. Many options are MyISAM specific but accepted for other storage engines,  
ie MAX\_ROWS, DELAY\_KEY\_WRITES etc.