Comments on: DrySQL: Not All I Had Hoped http://barelyenough.org/blog/2007/01/drysql-not-all-i-had-hoped/ … and there is much to be learned Thu, 02 Feb 2012 14:46:19 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Bryan Evans http://barelyenough.org/blog/2007/01/drysql-not-all-i-had-hoped/comment-page-1/#comment-9540 Bryan Evans Tue, 30 Jan 2007 20:05:25 +0000 http://pezra.barelyenough.org/blog/2007/01/drysql-not-all-i-had-hoped/#comment-9540 <p>Hi Peter</p> <p>I just wanted to follow up with you about your performance issues with DrySQL. I have just released a new version of the gem (0.2.0), which yields considerably better performance with all supported databases (in my test environment).</p> <p>As well, the latest release introduces the ActiveRecord::Base.generate_orm method, which will generate the associations and validations for all your model classes on demand, for those who prefer to take the performance hit upfront rather than incrementally during the application's uptime.</p> <p>DrySQL is still a work in progress, but hopefully you'll find the latest release to be an improvement over the previous.</p> <p>Cheers.</p> <ul> <li>Bryan</li> </ul> Hi Peter

I just wanted to follow up with you about your performance issues with DrySQL. I have just released a new version of the gem (0.2.0), which yields considerably better performance with all supported databases (in my test environment).

As well, the latest release introduces the ActiveRecord::Base.generate_orm method, which will generate the associations and validations for all your model classes on demand, for those who prefer to take the performance hit upfront rather than incrementally during the application’s uptime.

DrySQL is still a work in progress, but hopefully you’ll find the latest release to be an improvement over the previous.

Cheers.

  • Bryan
]]> By: Bryan Evans http://barelyenough.org/blog/2007/01/drysql-not-all-i-had-hoped/comment-page-1/#comment-7983 Bryan Evans Mon, 08 Jan 2007 17:05:23 +0000 http://pezra.barelyenough.org/blog/2007/01/drysql-not-all-i-had-hoped/#comment-7983 <p>Hi Peter</p> <p>You're absolutely right...DrySQL's performance with PostgreSQL is abysmal. My benchmarks revealed an average time of 15 seconds per model class for DrySQL to reflect on the information schema and retrieve the class's table metadata, and then fetch a row from the table. As you mentioned in your post, this becomes less worrisome in long-running production apps because the DB reflection is only done once per model class, but I do believe that performance is an issue that needs to be addressed.</p> <p>As for tweaking your environment, the only thing that comes to mind is choosing a Ruby-PostgreSQL driver. I had difficulty getting the Windows native driver to work in my environment, so I chose a pure Ruby driver in the interest of time since I only use PostgreSQL for testing. I'm told that the pure ruby driver is considerably slower than the native one, which may explain the poor performance I experience.</p> <p>I have admittedly neglected PostgreSQL in favor of other DBMSs that I have had more incentive to support, but I do plan to address performance with PostgreSQL as soon as I can. DrySQL's performance with most of the other DBMSs that it supports is considerably better than with PostgreSQL (i.e. less than a second for the same benchmark test with Oracle or MySQL), but I still plan to address the performance in those as well.</p> <p>In the short term, my plan is to work on optimizing the queries that DrySQL uses to retrieve DB schema information, and to offer user-configurable DB reflection so that programmers can choose when and how they would like DrySQL to reflect on their DB schema.</p> <p>Thanks for trying out DrySQL. If you care to share any more benchmarking information or offer any suggestions for improvement, I'm sure that readers of the DrySQL forums on RubyForge (myself included) would appreciate it. http://rubyforge.org/forum/?group_id=2438</p> <p>Cheers.</p> <ul> <li>Bryan</li> </ul> Hi Peter

You’re absolutely right…DrySQL’s performance with PostgreSQL is abysmal. My benchmarks revealed an average time of 15 seconds per model class for DrySQL to reflect on the information schema and retrieve the class’s table metadata, and then fetch a row from the table. As you mentioned in your post, this becomes less worrisome in long-running production apps because the DB reflection is only done once per model class, but I do believe that performance is an issue that needs to be addressed.

As for tweaking your environment, the only thing that comes to mind is choosing a Ruby-PostgreSQL driver. I had difficulty getting the Windows native driver to work in my environment, so I chose a pure Ruby driver in the interest of time since I only use PostgreSQL for testing. I’m told that the pure ruby driver is considerably slower than the native one, which may explain the poor performance I experience.

I have admittedly neglected PostgreSQL in favor of other DBMSs that I have had more incentive to support, but I do plan to address performance with PostgreSQL as soon as I can. DrySQL’s performance with most of the other DBMSs that it supports is considerably better than with PostgreSQL (i.e. less than a second for the same benchmark test with Oracle or MySQL), but I still plan to address the performance in those as well.

In the short term, my plan is to work on optimizing the queries that DrySQL uses to retrieve DB schema information, and to offer user-configurable DB reflection so that programmers can choose when and how they would like DrySQL to reflect on their DB schema.

Thanks for trying out DrySQL. If you care to share any more benchmarking information or offer any suggestions for improvement, I’m sure that readers of the DrySQL forums on RubyForge (myself included) would appreciate it.
http://rubyforge.org/forum/?group_id=2438

Cheers.

  • Bryan
]]>