Thanks for all the info, I think what I will do is make a test table and write a script to insert lots of rows with a similar pattern to what I would expect in the real world, then do some benchmarking of writing a new row at 100,000 rows, 200,000 rows, 500,000 rows... etc, and see how the table performs. I just assumed to index would slow down the frequent writes here but I'm thinking I should test that assumption, I'll post the benchmark results back next week...
On Thu, Aug 8, 2013 at 7:09 PM, Berend de Boer <[email protected]> wrote: > >>>>> "matt" == matt thomson <[email protected]> writes: > > matt> Usually, if a table is going to be this big and queried a > matt> lot, I will put an index on the columns that are > matt> queried. However, as well as being read from frequently, the > matt> table is also being written to frequently. As indexes take > matt> time to update on write, then updating the index constantly > matt> might end up slowing the table down so much that this method > matt> is not scalable. > > This is really a non-problem, unless you approach the size of > Facebook. > > > -- > All the best, > > Berend de Boer > > > ------------------------------------------------------ > Awesome Drupal hosting: https://www.xplainhosting.com/ > > -- -- NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected] --- You received this message because you are subscribed to the Google Groups "NZ PHP Users Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
