|
cracklover
Jan 28, 2015, 1:45 PM
Post #1 of 9
(6347 views)
Shortcut
Registered: Nov 14, 2002
Posts: 10162
|
Is it just me, or are all the pages taking forever to load?
GO
|
|
|
|
|
epoch
Moderator
Jan 28, 2015, 9:44 PM
Post #2 of 9
(6341 views)
Shortcut
Registered: Apr 28, 2005
Posts: 32163
|
It's a throwback to the days when the servers ran via hamster.
|
|
|
|
|
Jeff
Owner
Jan 29, 2015, 2:46 AM
Post #3 of 9
(6329 views)
Shortcut
|
Yeah, this new server still needs some tuning. The MySQL database is locking up a bit...
Been working on a few other problems that cropped up post migration, hoping to get to actual server tuning shortly.
|
|
|
|
|
cracklover
Feb 3, 2015, 2:04 PM
Post #4 of 9
(6272 views)
Shortcut
Registered: Nov 14, 2002
Posts: 10162
|
Seems *much* better now. But the my_topics (?do=my_topics;) still often is not working.
Black header bar -> My Stuff -> My Topics
GO
|
|
|
|
|
Jeff
Owner
Feb 6, 2015, 7:47 PM
Post #5 of 9
(6236 views)
Shortcut
|
cracklover wrote: Seems *much* better now. But the my_topics (?do=my_topics;) still often is not working. Black header bar -> My Stuff -> My Topics GO
Thanks for the heads up Gabe. I dug a bit deeper and changed a few database cache settings.
Is it better now?
(This post was edited by Jeff on Feb 6, 2015, 7:48 PM)
|
|
|
|
|
cracklover
Feb 6, 2015, 11:55 PM
Post #6 of 9
(6226 views)
Shortcut
Registered: Nov 14, 2002
Posts: 10162
|
Jeff wrote: cracklover wrote: Seems *much* better now. But the my_topics (?do=my_topics;) still often is not working. Black header bar -> My Stuff -> My Topics GO Thanks for the heads up Gabe. I dug a bit deeper and changed a few database cache settings. Is it better now?
Yes! Thanks! BTW, I'm also working on tuning a MySQL server. Lots of interesting settings to play with... Kind of fun!
GO
|
|
|
|
|
Jeff
Owner
Feb 7, 2015, 12:05 AM
Post #7 of 9
(6220 views)
Shortcut
|
You probably already know this, but innodb_buffer_pool_size & innodb_buffer_pool_instances are your friends. I'd completely forgotten when we migrated to change the defaults, that's why the site was slow... buffer pool size of 128MB. It's 20 GB now which should be far more than we need. :-D
Unfortunately, this site has 24 tables that have FULLTEXT indexes, so can't be converted to InnoDB without changing MySQL server version, and I'm hesitant to do that for several reason... those are the likely culprits at this point if any part of the site is running slow.
(This post was edited by Jeff on Feb 7, 2015, 12:05 AM)
|
|
|
|
|
cracklover
Feb 8, 2015, 3:29 PM
Post #8 of 9
(6192 views)
Shortcut
Registered: Nov 14, 2002
Posts: 10162
|
Jeff wrote: You probably already know this, but innodb_buffer_pool_size & innodb_buffer_pool_instances are your friends. I'd completely forgotten when we migrated to change the defaults, that's why the site was slow... buffer pool size of 128MB. It's 20 GB now which should be far more than we need. :-D Unfortunately, this site has 24 tables that have FULLTEXT indexes, so can't be converted to InnoDB without changing MySQL server version, and I'm hesitant to do that for several reason... those are the likely culprits at this point if any part of the site is running slow.
We should probably take this conversation offline, but two quick thoughts:
1 - Starting with version 5.6 innoDB tables can support Full-Text search. So you should consider moving those from MyISAM. But there are still some reasons to keep some tables in the older engine. If you choose to do so, consider point 2.
- key_buffer_size defines size in memory for index blocks to share from MyISAM tables. The default for this on your DB is 16 M - tiny! If you have some large and vital indexed MyISAM tables consider upping this variable to as much a quarter of the memory available on your machine.
Good luck!
GO
|
|
|
|
|
lena_chita
Moderator
Mar 5, 2015, 4:28 PM
Post #9 of 9
(6024 views)
Shortcut
Registered: Jun 27, 2006
Posts: 6087
|
It seems to be slower again the last couple days?
|
|
|
|
|
|
