Comments on: MySQL optimizations: indexes http://www.westhost.com/blog/2009/01/20/mysql-optimizations-indexes/ News, Announcements & More Tue, 01 Nov 2011 13:20:05 +0000 hourly 1 By: videofeedback http://www.westhost.com/blog/2009/01/20/mysql-optimizations-indexes/comment-page-1/#comment-16440 videofeedback Wed, 30 Dec 2009 03:11:49 +0000 http://www.westhost.com/blog/?p=153#comment-16440 I am installing a java based media browser app [hopefully if I can debug it] on my site here at westhost. As part of it's abilities it uses the yahoo searchAPi to pull a directory of videos. Yahoo leads me to believe that with a properly constructed rss feed in xml form and parked in say my videos directory, that the yahoo search engine will come crawl it, and then the urls for my videos will be available through the java based media browser. Thus releiveing me of putting all 800+ videos into the MySQL database. Which I won't mind doing but I want to do this rss feed thing with yahoo first. anyone got any input on what the format of the xml rss feed file needs to look like? Like this maybe: (xml header) video:http://www.videofeedback.com/Marquis/video1.flv thumb:http://www.videofeedback.com/Marquis/video1_thumb.jpg and so on? thanks VFB I am installing a java based media browser app [hopefully if I can debug it] on my site here at westhost.
As part of it’s abilities it uses the yahoo searchAPi to pull a directory of videos.

Yahoo leads me to believe that with a properly constructed rss feed in xml form and parked in say my videos directory, that the yahoo search engine will come crawl it, and then the urls for my videos will be available through the java based media browser. Thus releiveing me of putting all 800+ videos into the MySQL database. Which I won’t mind doing but I want to do this rss feed thing with yahoo first.

anyone got any input on what the format of the xml rss feed file needs to look like?

Like this maybe:

(xml header)
video:http://www.videofeedback.com/Marquis/video1.flv
thumb:http://www.videofeedback.com/Marquis/video1_thumb.jpg

and so on?

thanks
VFB

]]> By: ecommerce http://www.westhost.com/blog/2009/01/20/mysql-optimizations-indexes/comment-page-1/#comment-5612 ecommerce Wed, 04 Feb 2009 13:22:56 +0000 http://www.westhost.com/blog/?p=153#comment-5612 Great article thanks Great article thanks

]]> By: Brian Cressall http://www.westhost.com/blog/2009/01/20/mysql-optimizations-indexes/comment-page-1/#comment-4142 Brian Cressall Wed, 21 Jan 2009 16:50:03 +0000 http://www.westhost.com/blog/?p=153#comment-4142 Indexes are great optimization tools. One caveat is that there is a performance cost to maintain an index. It is typically not a huge cost, but it still exists. When you insert or delete a record, the index must be updated. When you update a record, an index may have to be updated if your update affects the index. Some people think that indexes are a magic bullet and will index every column in their table. While that can help you search on anything, it causes a performance hit and is usually unnecessary. The rule of thumb is to only index fields that you search on. In a future article, maybe we could talk about composite indexes and how the order of the indexed fields is important. Many people get confused on how indexes work and will create single-field indexes instead of a more appropriate composite index. Indexes are great optimization tools. One caveat is that there is a performance cost to maintain an index. It is typically not a huge cost, but it still exists. When you insert or delete a record, the index must be updated. When you update a record, an index may have to be updated if your update affects the index.

Some people think that indexes are a magic bullet and will index every column in their table. While that can help you search on anything, it causes a performance hit and is usually unnecessary. The rule of thumb is to only index fields that you search on.

In a future article, maybe we could talk about composite indexes and how the order of the indexed fields is important. Many people get confused on how indexes work and will create single-field indexes instead of a more appropriate composite index.

]]>