indexes.
Perhaps I'm misunderstanding you here, but my MySQL tables already *define* indexes on the name column. What more could be done?
Have you turned on mysql's slow query logging? Sometimes it's a painful query that's not quite what you expect. Once you know what query you're talking about, "EXPLAIN ..." can be lots of help.
The problem is that it's selecting 700 nodes, and all the metadata for them, which is just a lot of frickin data. (The latest database dump is 1.95 meg.)
(Do you mean megs or gigs?)
The loading half of CPAN happens on every page. The loading 1.95MB of data and building the associated structures inside the request (attaching all the metadata and so on) only happens on the index page.
Has anyone done a FastCGI version of the openguides CGI? That can help a LOT.
I'm not saying that the speed isn't related to other aspects, but at least some of this will start to be limited by the database once it gets bigger.
A couple of orders of magnitude bigger. at 2 megs of data, everything should be coming straight out of ram inside mysql.
-- Chris
-- OpenGuides-Dev mailing list - OpenGuides-Dev@openguides.org http://openguides.org/mm/listinfo/openguides-dev