query performance

2005-02-16 Thread Ryan McCullough 
Can I post a query to this list and ask for help optimizing it?

-- 
Ryan McCullough
mailto:[EMAIL PROTECTED]

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: Data in different tables or is one big table just as fast?

2005-02-15 Thread Ryan McCullough 
how about purging rows older than a month? Do you need to keep them?
Archive them them to another database?

Actually, I got a better idea. Have your master db which is huge and
holds everything. Then on a seperate DB run a table for each feedid
with the last 100 feeds for that id.

Have a cron job that runs continually updating those tables with current data.

get it?


On Tue, 15 Feb 2005 23:02:38 +0100, Jacob Friis Larsen
[EMAIL PROTECTED] wrote:
  We have a table that grow by 200MB each day.
  Should we put data in different tables or is one big table just as fast?
  
   The table contains data from RSS and Atom feeds.
   Most users only need to see the newest items.
   A select could look like this: SELECT title, desc FROM items WHERE
   feedid = 25 ORDER BY id DESC LIMIT 10
 
  I would, however, be seriously concerned about diskspace if a table is 
  adding
  200 MB a day with no archiving/compression/purges.
 
 What if we use COMPRESS() for the text in old rows?
 
 Jacob
 
 --
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
 
 


-- 
Ryan McCullough
mailto:[EMAIL PROTECTED]

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: queries slower on InnoDB

2005-02-14 Thread Ryan McCullough 
what about other functions like doing a min() or max()? are those slow
limitations of innodb tables as well?


On Mon, 14 Feb 2005 15:52:21 -0600, Eric Bergen [EMAIL PROTECTED] wrote:
 Total row count is cached in the header for MyISAM tables. InnoDB has
 no such mechanism for this because transactions make it impossible to
 keep an exact row count.  In order for InnoDB to get a row count it
 has to do a full scan inside a transaction which will take a long
 time. One way around this is to maintain row count in another table.
 
 For show table status it's better to only check the tables you need.
 Example: show table status like 'my_table'
 
 I'm not aware of any plans to speed up either of these commands on InnoDB.
 
 
 On Mon, 14 Feb 2005 12:06:09 -0500, Zhe Wang [EMAIL PROTECTED] wrote:
  Hi, there,
 
I am in the middle of replacing a MyISAM database with InnoDB.
  Queries show table status and select count are extremely slow which
  gave me some pain. I am wondering if there are any other queries on
  InnoDB that are significantly slower than those on MyISAM other than
  these two? And does MySQL have any plan to speed up this kind of queries?
 
Thank you very much in advance for your reply!
 
  Regards,
  Zhe
 
  --
  MySQL General Mailing List
  For list archives: http://lists.mysql.com/mysql
  To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
 
 
 
 --
 Eric Bergen
 [EMAIL PROTECTED]
 
 --
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
 
 


-- 
Ryan McCullough
mailto:[EMAIL PROTECTED]

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]