There is no number N where N turns performance unacceptable. It's a number that you'll have to derive yourself, based on parameters of acceptability that you have to try yourself.

It's misguided to try to find a magic number. What you'll have is a curve of performance, probably something like this

Records => response time
100 => effectively instant
1000 => 1 sec
10000 => 3 sec
100000 => 10 sec
1000000 => 5 minutes
Once you derive that curve, you can say "OK, if we want to keep performance around 10 second response time, we can't have more than 100000 records, and if we want more than that, we're going to have to go to a bigger/different system."

The other part of it is to define very carefully what that performance acceptability is. Is it OK if the user has to wait 1 second to do an update? 10 seconds? A minute? Define those, in writing, and make sure that you get that approved by anyone who could squawk. There's nothing worse than having your requirements changed out from under you, when your boss says "Hey, it's taking too long to update", because you thought that a 5-second lag was acceptable.

xoxo,
Andy
--
Throw down the gun and tiara and come out of the float!

In reply to Re: When is a flat file DB not enough? by petdance
in thread When is a flat file DB not enough? by TrinityInfinity

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.