[SOLVED] Should I be thinking about Optimization?

[NeoMarine]

I have a mysql table which records every view on a certain page, basically it tracks the viewers I.P address, the page ID, the date, etc.

 

I am curious if maybe this was a poor approach... I'm wondering what kind of number of records MYSQL can handle before it gets noticeably slow.

 

So far there are 11,893 total entries into the table, over a period of about 3 months, however I expect it will only grow at an increased rate and I'm curious if perhaps I should simply change the design to tracking the views some other way..

 

What do you suggest?

[cooldude832]

The question becomes do you need to track all that data.

 

If you only want daily numbers maybe make a new row for each day vs each entry

 

 

11.893 records isn't an exsuperent number but its on its way.

[obsidian]

11,893 records isn't an exsuperent number but its on its way.

 

I wouldn't even go that far. I'm constantly working with MySql tables with well over half a million records in them with relatively little delay. It comes back to how well indexed your table is and what type of queries you are running against it. Fenway would probably be the best to really answer this, but in my experience, I haven't noticed significant delays on well indexed tables until it gets into the hundreds of thousands of unique records in those that are actively queried.

[NeoMarine]

I don't really need the data, but I may in the future.

 

I think I will hold off changing my table structure until the point where I notice a little bit of delay, and am sure I don't need the data.

 

Thanks for your help!