DrByte:
"top" could be used to find out what server process is hogging the CPU while "things start spinning". It's a server console command-line utility. You need SSH to do it.
Similar could be done with "mytop", if you have it, for most demanding SQL queries happening.
Both are real-time tools.
Further, you could check your database schema to ensure that all original indexes are actually intact. (export schemas from live and from a brand new database, and compare them with something like winmerge). Again, this wouldn't be a problem unique to 1.3.9h, since there were no schema changes since 1.3.9a.
DrByte, thanks for the clarification. Although have root access, I am clueless when it comes to "top" and "mytop" I will do some reading about it as well as contact our host company. We are on a dedicated server so I have access to be dangerous :) but I try not to touch things I don't understand.
I am assuming the db schema you referenced is comparing the structure of our production to a clean 1.3.9. If that's the case I didn't notice any significance difference. If I am comparing the wrong thing please set me straight.
One obvious thing I noticed is that the clean structure of 1.3.9 includes collation information which my production version doesn't so I don't know if that's significant.
Here's an example of clean 1.3.9
CREATE TABLE IF NOT EXISTS `address_book` (
`address_book_id` int(11) NOT NULL auto_increment,
`customers_id` int(11) NOT NULL default '0',
`entry_gender` char(1) collate latin1_general_ci NOT NULL default '',
`entry_company` varchar(64) collate latin1_general_ci default NULL,
`entry_firstname` varchar(32) collate latin1_general_ci NOT NULL default '',
`entry_lastname` varchar(32) collate latin1_general_ci NOT NULL default '',
`entry_street_address` varchar(64) collate latin1_general_ci NOT NULL default '',
`entry_suburb` varchar(32) collate latin1_general_ci default NULL,
`entry_postcode` varchar(10) collate latin1_general_ci NOT NULL default '',
`entry_city` varchar(32) collate latin1_general_ci NOT NULL default '',
`entry_state` varchar(32) collate latin1_general_ci default NULL,
`entry_country_id` int(11) NOT NULL default '0',
`entry_zone_id` int(11) NOT NULL default '0',
PRIMARY KEY (`address_book_id`),
KEY `idx_address_book_customers_id_zen` (`customers_id`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1 COLLATE=latin1_general_ci AUTO_INCREMENT=3 ;
Here is an example of production:
CREATE TABLE IF NOT EXISTS `address_book` (
`address_book_id` int(11) NOT NULL auto_increment,
`customers_id` int(11) NOT NULL default '0',
`entry_gender` char(1) NOT NULL default '',
`entry_company` varchar(32) default NULL,
`entry_firstname` varchar(32) NOT NULL default '',
`entry_lastname` varchar(32) NOT NULL default '',
`entry_street_address` varchar(64) NOT NULL default '',
`entry_suburb` varchar(32) default NULL,
`entry_postcode` varchar(10) NOT NULL default '',
`entry_city` varchar(32) NOT NULL default '',
`entry_state` varchar(32) default NULL,
`entry_country_id` int(11) NOT NULL default '0',
`entry_zone_id` int(11) NOT NULL default '0',
PRIMARY KEY (`address_book_id`),
KEY `idx_address_book_customers_id_zen` (`customers_id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 AUTO_INCREMENT=33956 ;
I see a consistent pattern of the colation information on new 1.3.9 structure but not the one I downloaded for production.
Not sure if this is something significant or not.
Thanks for your input.
