Results 1 to 2 of 2
  1. #1
    Join Date
    Feb 2010
    Posts
    2

    Unanswered: Rapidly Growing Database

    I built a member based analytics system. All data is stored in a mysql db.

    This system is growing rapidly and I have several tables that are approaching a gig in size. I don't see a lot of lag yet but I am worried about the future.

    Since this is a member based system should I split the tables up among several tables by member or should i separate it by a database for each member?

    What would be the best approach to this?

    Also what size is a troublesome size for a mysql table or db?

    Thanks in advance!

  2. #2
    Join Date
    Jun 2007
    Location
    London
    Posts
    2,527
    Quote Originally Posted by thinknew
    I built a member based analytics system. This system is growing rapidly and I have several tables that are approaching a gig in size.
    We can only imagine what a "member based analytics system" is but a gig of data for a relatively new system is a little worrying. Can you give any info on what it is you're storing? Why is it growing so rapidly? is it because you're getting too many members or is their an issue with the design? Perhaps:
    • you're storing too much data - (a gig of growth for a new system is a lot)
    • you're not cleaning old data?
    • you should charge by usage and then the amount of data being stored will reduce?
    • if you envisage many more users (and a lot more growth) then the system should be installed on the client side rather than on a server?

    Splitting tables is usually a bad idea and nearly always results in poorer overall system performance and way more maintenance issues.

    Mike

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •