meta user
network profile
| bio | website | sparrowtail.com |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 2 years, 1 month |
| seen | May 21 at 9:00 | |
| stats | profile views | 12 |
Chief Technical Officer at Analytics SEO - it's a startup, which means I'm actually developer, architect, project manager, operations manager, tester, technical support, and everything else technical.
I specialise in Apache/MySQL/PHP development, especially using Drupal, but also have experience building high-performance high-load web applications on IIS/MSSQL/C#/ASP.Net
There's more at LinkedIn
I specialise in Apache/MySQL/PHP development, especially using Drupal, but also have experience building high-performance high-load web applications on IIS/MSSQL/C#/ASP.Net
There's more at LinkedIn
|
Sep 3 |
accepted | Simple queries taking ages to run after changing from MyISAM to InnoDB |
|
Sep 3 |
comment |
Simple queries taking ages to run after changing from MyISAM to InnoDB I've now finished adding the primary key to the inbound_link_changes table, and also changed link_id in that table to a bigint. Performance is now much better - 0.2 seconds for my original sample query. We are now reviewing all our InnoDB tables to ensure they all have a sensible primary key. Thanks for helping out with this! |
|
Aug 30 |
comment |
Simple queries taking ages to run after changing from MyISAM to InnoDB Thanks Rick - that server has 24GB RAM, so we should be fine with the 8GB buffer pool. We're not using any explicit locking. |
|
Aug 30 |
comment |
Simple queries taking ages to run after changing from MyISAM to InnoDB This was indeed changed during the conversion, and we're currently converting ilc.link_id to a bigint too. According to blog.dbadeva.com/2008/07/… this is unlikely to make much difference, but I guess this could be the cause of the problem - we'll see when it's finished. |
|
Aug 29 |
comment |
Simple queries taking ages to run after changing from MyISAM to InnoDB Thanks for the detailed suggestions. These are definitely changes that I will make to the inbound_link_changes table, but does this explain why the performance changed so much when I changed the storage engine of the inbound_links table from MyISAM to InnoDB? If the lack of a primary key on inbound_link_changes was going to cause a performance issue, wouldn't we have seen that against the MyISAM inbound_links table too? |
|
Aug 29 |
awarded | Editor |
|
Aug 29 |
revised |
Simple queries taking ages to run after changing from MyISAM to InnoDB Added additional data |
|
Aug 29 |
asked | Simple queries taking ages to run after changing from MyISAM to InnoDB |
|
Apr 13 |
awarded | Scholar |
|
Apr 13 |
accepted | Is tuning the innodb_buffer_pool_size important on Solaris ZFS? |
|
Mar 29 |
awarded | Student |
|
Mar 29 |
comment |
Is tuning the innodb_buffer_pool_size important on Solaris ZFS? Apologies for the double post at link but I'm not sure how big the audience is here! |
|
Mar 29 |
asked | Is tuning the innodb_buffer_pool_size important on Solaris ZFS? |
