On Wed, Jul 28, 2010 at 6:52 PM, Jonathan Stott <[email protected]>wrote:
> On 27 July 2010 20:02, Randy Fischer <[email protected]> wrote: > > > > Well, that too only gives a doubling, surprisingly. The > > DateTime cast is still done in that case, BTW. > > > > Since they're timestamps, are they actually all within the unix epoch? > If so, you could make them Time, rather than DateTime, which should > be faster. > > Nice! It works well with my data - (which for external reasons has to be an underlying DateTime column type). Unfortunately telling DM that they were just strings only gave a doubling (~6000 records/sec) from my heavy-handed approach, ~3000 records/sec. Telling DM it's a Time property falls somewhere in the middle, as expected I guess - ~4800 records/sec. I'm pretty convinced at this point that it's the model object creation per row that's killing me here. Thanks for the suggestion, this has been a fun process. -Randy Fischer -- You received this message because you are subscribed to the Google Groups "DataMapper" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/datamapper?hl=en.
