This benchmark inserts `nil` for the timestamps when using Sequel. These are not benchmarking the same thing
-
-
we got to fix that then ... let me have a quick look
1 reply 0 retweets 0 likes -
Replying to @samsaffron @bmarkons
Surprised you would ever accept a 5x difference to be true here TBH. Both of these are going to be dominated by IO
2 replies 0 retweets 0 likes -
lets see, 376 vs 71 ... yeah that is 5x I can accept that
1 reply 0 retweets 0 likes -
Replying to @samsaffron @bmarkons
Again, you aren't casting the dates in your raw benchmark. Apples to oranges.
2 replies 0 retweets 0 likes -
I absolutely am, using a coder
1 reply 0 retweets 0 likes -
Replying to @samsaffron @bmarkons
No, you aren't. puts results.getvalue(i, 2).class.name It's a string.
3 replies 0 retweets 0 likes -
@jeremyevans0 wrote a monster implementation of date parsing in sequel_pg https://gist.github.com/SamSaffron/1f743f9223af5fa44ffbfa4cf9c2c77f … faster than built in2 replies 0 retweets 0 likes -
Replying to @samsaffron @bmarkons
Heh well if we're going to do comparisons on code written in not-Ruby, just wait until you see our new driver... ;P
1 reply 0 retweets 1 like -
;P ... trying to get comparisons out in the public for all available implementations, if you have some time would love a review on rubybench
2 replies 0 retweets 0 likes
I do think it's funny how it's pretty easy to accidentally make raw pg slower than AR https://gist.github.com/sgrif/38e1d3f59cf0ed59646dbbee07236a11 …
-
-
absolutely, that is why I should really publish sql_mapper at some point, you can actually even marginally beat raw with a clean mapper
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.