Linked by Thom Holwerda on Fri 6th May 2011 21:00 UTC
Thread beginning with comment 472176
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Features
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
Linked by Thom Holwerda on 04/16/13 9:29 UTC
Linked by Thom Holwerda on 04/15/13 22:44 UTC
Linked by Thom Holwerda on 04/14/13 18:22 UTC, submitted by MOS6510
More Features »
Sponsored Links



Member since:
2005-11-13
To tell you the truth, that was something I forgot, but
checked it right now an it's using InnoDB
Don't know how well Drupal7 uses PostgreSQL, but it was just an example of something I tried recently to determine how to improve my site speed. Tested it with MySQL, PostgreSQL and SQLite, and the speed compassion was 2:1:1.
Testing other CMSs the ratio varies, but MySQL is always faster.
Well, that's something that most "end users" can't control, since most people gets some software and set it to work without ever looking at the code.
In small databases made by myself I can't feed any speed difference, but I'm positively sure my code is wasting time, but when you use something that "supports PostgreSQL" and there is a noticeable performance difference, it's at least annoying.
I'm not saying it's PostgreSQL's fault, but if that's a known sore spot and something many people use, it should get some attention to try and make it better.
Maybe when I get to test 9.x there will be some improvements.