A vote of confidence for 0.14.4 -> 1.0:  We've successfully moved our
app to 0.14.4.  We have the following code stats:

+----------------------+-------+-------+---------+---------+-----+-------+
| Name                 | Lines |   LOC | Classes | Methods | M/C | LOC/M |
+----------------------+-------+-------+---------+---------+-----+-------+
| Helpers              |   412 |   214 |       1 |      19 |  19 |     9 |
| Controllers          |   976 |   698 |       9 |      61 |   6 |     9 |
| APIs                 |     0 |     0 |       0 |       0 |   0 |     0 |
| Components           |     0 |     0 |       0 |       0 |   0 |     0 |
|   Functional tests   |  2213 |  1687 |      26 |     165 |   6 |     8 |
| Models               |  1278 |   684 |      26 |      59 |   2 |     9 |
|   Unit tests         |  2563 |  1912 |      19 |     219 |  11 |     6 |
| Libraries            |   562 |   267 |       4 |      27 |   6 |     7 |
+----------------------+-------+-------+---------+---------+-----+-------+
| Total                |  8004 |  5462 |      85 |     550 |   6 |     7 |
+----------------------+-------+-------+---------+---------+-----+-------+
  Code LOC: 1863     Test LOC: 3599     Code to Test Ratio: 1:1.9

We're hitting both postgres and oracle successfully now that we've
patched for #3133.

Downside:  we've seen a pretty significant slowdown on Oracle when
running our test suite (this may not be present as a production-time
slowdown -- we haven't measured it).  Where prior to the move to 0.14.4
w/ #3133 we were seeing postgres running about 50% faster than Oracle,
now Postgres is roughly the same speed as before, but Oracle is
significantly slower.

Postgres:
unit: Finished in 24.523295 seconds. / 201 tests, 733 assertions, 0 failures, 0 
errors
func: Finished in 14.954842 seconds. / 135 tests, 597 assertions, 0 failures, 0 
errors

Oracle:
unit: Finished in 83.750658 seconds. / 201 tests, 733 assertions, 0 failures, 0 
errors
func: Finished in 78.09833 seconds.  / 135 tests, 597 assertions, 0 failures, 0 
errors

Previously we would've expected Oracle to run in ~36-38 seconds, and
~22-24 seconds, so the difference is quite visible.

Neither database is optimized (for better or for worse), and while we're
happy to see the open source alternative leading the closed source
behemoth, it's a bit unfair if the difference is to be found in
oci_adapter.rb.

Rick
-- 
 http://www.rickbradley.com    MUPRN: 3
                       |  In my grand scheme
   random email haiku  |  of things, I plan to have
                       |  some random content.
_______________________________________________
Rails-core mailing list
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails-core

Reply via email to