GET 24/7 LIVE HELP NOW

Announcement

Announcement Module
Collapse
No announcement yet.

Performance compare PostgreSQL vs MySQL

Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Performance compare PostgreSQL vs MySQL

    Not many info. on the Internet comparing their performance in real world usage, anyone with experience want to comment?

  • #2
    There is no such thing as real world usage, there are thousands of applications in real world and all of them are different.

    In general you can build efficient application with both database systems, it is the question of your experience, bias and particular requirements. For example PostgreSQL often handles complex queries better while MySQL has power of multiple storage engines.

    Comment


    • #3
      As a MySQL expert, what do you think abt the following comments:

      from:

      http://www.enterprisedb.com/solutions/gotmysql.do

      MySQL users know firsthand that MySQL is most effective for read-only environments and the web/edge tier - but not for applications in demanding OLTP environments, requiring enterprise-class reliability, availability, and scalability.

      Comment


      • #4
        Well,

        It is as usually a lot of marketing talk. In reality you should look into what is important for your particular application and make a choice based on this information.

        Too often however people do not like to spend time investigating and simply base decisions on rumors which can be outdated such as "MySQL does not support transactions" or silly "MySQL does not work with tables more than 10.000 rows"

        MySQL is not perfect as any other Database Solution but be careful reading marketing talk as it usually only highlights benefits of home made solutions and not speaking about drawbacks.

        Comment


        • #5
          Yeah, and what I really do not like is that "sales by fear", like the "users will hit a wall". Speaking of Wall, wasnt it Larry who said "there is more than one way to do it"?

          I guess the same principles count here, too!

          Also: you can create some really bad solutions with the right software. I know what I am talking about, when I look at some of my code

          Cheers,
          Ralf

          Comment


          • #6
            When It comes to databases I personally follow the rule "whatever works". Both database engines are scalable, and highly efficient even with large datasets. In reality I guess its hard to compare because you would have to start with some engine, grow database (which make time time), and then switch to different database engine importing data from the old one, which can be a tremendous task to do. It could be a good subject to thesis though .
            Last edited by TomD; 07-08-2014, 10:12 AM. Reason: Spam link removed from end of post

            Comment

            Working...
            X