Hi,

I am very new to Movable Type, and I have been making a few modifications to the default install (4.1). I have disabled all except the necessary plugins, which has not helped my issue. When visiting mt.cgi, my browser takes at least one minute to load, and about the same time when navigating between pages within mt.cgi. There is one functional difference within mt.cgi since I noticed the problem. Within the Design menu, only the Templates menu option appears, not the other two options. Within the Templates page, only the Mail Footer template is in the list. Very strange.

I have added two custom Widgets, both simply links that I wanted to place in the navigation bar (Photo page, archive page), nothing fancy.


Any ideas what the problem could be? Thanks for any help!

Andy

Anything in the server logs?

Try running CHECK TABLES on the database to see if it reports any problems.

Just ran the CHECK TABLES, everything reported back OK.

Nothing out of the ordinary in the logs.

My two custom widgets are simple HTML links to other pages on my domain. Would this cause a problem, or is it a normal thing to do? Other than that, I really haven't done anything special to the install.

They should not cause a problem, if you remove them does speed improve?

Another cause may be misconfigured Image::Magick

Ok, this just got weird. I decided that since it was such a young blog, to just wipe and start fresh to avoid any mistakes. I redownloaded the MT software, created a new blog, and it is STILL slow. This means it has to do with my hosting / the cgi scripts. I use Dreamhost, and have Fast CGI support enabled. Heard of this type of problem before? Thanks in advance.

Andy

I'm having the same problems. Sometimes it runs at normal speed, but lately it's been really really slow most of the time. I'm on Bluehost. Rest of my site works fine, but working in MT's control panel, it takes a long time to open a page.

I would start by disabling the stats widget on the front page.

Hi ONM,

I've seen you mention this before and I'd sure like to try it, but ... where is it? Where's the switch for this thing? Is it in MT 4.2 by default?

Thanks very much

I see the same issue. MT 4.1 - that dashboard is really slow out of the box - for almost all types of requests. I strace'ed the mt.cgi process and it seems to be making a lot of stat calls on non-existent files. I wonder if this is contributing to the slowness.

stat64("/var/www/vipul.net/mt/plugins/spamlookup/lib/StyleCatcher/L10N/en_us.pmc", 0xbffff1d0) = -1 ENOENT (No such file or directory)
stat64("/var/www/vipul.net/mt/plugins/spamlookup/lib/StyleCatcher/L10N/en_us.pm", 0xbffff0e0) = -1 ENOENT (No such file or directory)
stat64("/var/www/vipul.net/mt/plugins/WidgetManager/lib/StyleCatcher/L10N/en_us.pmc", 0xbffff1d0) = -1 ENOENT (No such file or directory)
stat64("/var/www/vipul.net/mt/plugins/WidgetManager/lib/StyleCatcher/L10N/en_us.pm", 0xbffff0e0) = -1 ENOENT (No such file or directory)
stat64("/var/www/vipul.net/mt/plugins/WXRImporter/lib/StyleCatcher/L10N/en_us.pmc", 0xbffff1d0) = -1 ENOENT (No such file or directory)
stat64("/var/www/vipul.net/mt/plugins/WXRImporter/lib/StyleCatcher/L10N/en_us.pm", 0xbffff0e0) = -1 ENOENT (No such file or directory)
stat64("/var/www/vipul.net/mt/plugins/Textile/lib/StyleCatcher/L10N/en_us.pmc", 0xbffff1d0) = -1 ENOENT (No such file or directory)
stat64("/var/www/vipul.net/mt/plugins/Textile/lib/StyleCatcher/L10N/en_us.pm", 0xbffff0e0) = -1 ENOENT (No such file or directory)
stat64("/var/www/vipul.net/mt/plugins/StyleCatcher/lib/StyleCatcher/L10N/en_us.pmc", 0xbffff1d0) = -1 ENOENT (No such file or directory)
stat64("/var/www/vipul.net/mt/plugins/StyleCatcher/lib/StyleCatcher/L10N/en_us.pm", {st_mode=S_IFREG|0644, st_size=386, ...}) = 0
open("/var/www/vipul.net/mt/plugins/StyleCatcher/lib/StyleCatcher/L10N/en_us.pm", O_RDONLY|O_LARGEFILE) = 6

# Movable Type version: 4.1
# Operating system: linux
# Perl version: 5.8.8

Same here -- though without the custom widgets. It seems to be centered around the comments page in the blog dashboards. Whenever we enter that page, no matter if comments is enabled or not the mt.cgi that is started for the page will start goobling server memory. This continues until the process is killed.

While it is running it will within minutes get up to all available RAM in the server. (2GB in the production server & 1GB in the dedicated test machine.) In the process, because there's no swap space left and Linux has to start tap dancing and juggling at the same time, all other processes start backing up behind the mt.cgi and users get turned away, MySQL starts refusing connections, vBulletins starts throwing errors because MySQL isn't talking to it.

How many comments per page do you have set up for the view?

How many comments do you have?