There is a site, a file index pkhp. There is a database, there is a table of content, well, of course there are articles. If the index pkhp? = 6, it shows the article id = 6 and so on. Well, there are 4-5 other pages, such as about us, write to us, etc. At the moment, the number of articles is about 400, but they say that if there are more than 1000 articles (well, many), then the site will be "buggy." How true is this?

    4 answers 4

    Nonsense, the speed of receipt will depend on the characteristics of the server, if the id field in the table is PRIMARY KEY with a smallint type and a length of 5, then there will be no problems with receiving. In this case, the id can be a little more than 65000. If you want more, then the field type is mediumint and length is 8, then up to 16 million

      It's a lie. =)
      1000 articles for MySQL even on weak hosting is a simple task, even if you use full-text search.
      Problems can begin if a crowd of hamsters comes to the site. But there and the business card can collapse.

      • What kind of hamsters? - meravaz
      • Users, in large quantities)) - Dem
      • That's right, the volume of records in the database is in no way related to the number of requests. - Palmervan

      I remember a long time ago when I started learning php and sql for some reason I also thought that the speed of work depended on it very much ... Well, in general, the scary for cycle threw 2 million records into the table articles, the sampling speed practically did not affect :)
      PS: Especially since you have a sample by induction, but when I did it, I still had little understanding of what it was, well, in general, they were not there except the primary id, and the sample was made according to the title ...

        1000 articles, if you don’t pull everything at once, if the server has at least 512 RAM, there will be no problems, make a selection according to the already mentioned ID and specify only the necessary lines, well, if everything is really bad, or the project is designed for a large load .. index the main affected fields, for faster access to them (when indexing, the base will take more space on hard drive)