Professional Web Applications Themes

Mysql performance for online applications - MySQL

Hi, Just asking out of my curiosity. Which of these can hamper performance of my online applications? Having multiple small databases open concurrently or huge size of one single database? What happen for its long term run?...

  1. #1

    Default Mysql performance for online applications

    Hi,

    Just asking out of my curiosity. Which of these can hamper performance
    of my online applications?

    Having multiple small databases open concurrently or huge size of one
    single database? What happen for its long term run?

    adzir Guest

  2. #2

    Default Re: Mysql performance for online applications


    "adzir" <com> schreef in bericht
    news:googlegroups.com... 

    That is a tricky one. What is huge?
    If you have lots of queries, that will join those small tables, you will pay
    a perfomance penalty.
    Having one huge database might get you to the limits of the OS.


    Hans Guest

  3. #3

    Default Re: Mysql performance for online applications


    "Hans H" <nl> wrote in message
    news:4624e4a4$0$990$kpnplanet.nl... 
    >
    > That is a tricky one. What is huge?
    > If you have lots of queries, that will join those small tables, you will
    > pay
    > a perfomance penalty.
    > Having one huge database might get you to the limits of the OS.
    >[/ref]

    Funny you mentioned this, because in todays lessons we have learned about
    this.
    It's safer to have multiple small databases because of "update anomalies".
    My tech-English is not that good, so I find it difficult to explain. Google
    it.

    Duz Guest

  4. #4

    Default Re: Mysql performance for online applications

    Duz schrieb: 

    Sorry, that's simply wrong (though it may be due to a misunderstanding).

    To avoid update anomalies, you normalize a table, which (usually) means
    that you split the data into multiple tables.
    Having multiple databases doesn't help.

    BTW the downside is that you can't JOIN across databases. IOW splitting
    into multiple databases is advised if the data should be kept separate.
    (Say, a "productive" and a "test" database. Or to enforce safe harbor
    constraints, to prevent idle administrators from connecting data that
    must remain unconnected.)
    I.e. multiple database considerations are about ensuring strategic
    properties, while having multiple tables and normalization and avoiding
    update anomalies is more "tactical".

    Regards,
    Jo
    Joachim Guest

Similar Threads

  1. mysql performance issues too many connections
    By marcfischman@gmail.com in forum MySQL
    Replies: 2
    Last Post: September 7th, 07:43 PM
  2. Compiling Mysql for high performance
    By forrie@gmail.com in forum MySQL
    Replies: 5
    Last Post: July 17th, 05:46 PM
  3. PHP vs Java performance on MySQL
    By Rajesh Kapur in forum PHP Development
    Replies: 2
    Last Post: August 14th, 11:20 PM
  4. Largest applications that PHP/MYSQL can build?
    By Louis-Philippe Huberdeau in forum PHP Development
    Replies: 2
    Last Post: July 16th, 11:26 PM

Bookmarks

Posting Permissions

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

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139