That's what I'm doing. I'm just creating a new byte[]. Anyway, the problem is not with the dirty check. I've uploaded an snapshot of a dotTrace session (http://twitpic.com/2t0lo5/full). That snapshot is taken after update the varbinary field from 3 bytes to 2MB. As you can see, the most expensive operation is SqlCommand.ExecuteNonQuery. However, the same ExecuteNonQuery in raw sql takes less than a second.
On Tue, Sep 28, 2010 at 10:59 AM, Nexus <[email protected]> wrote: > Juanma, > > As a general advice don't update blobs think of them as > ValueObjects(DDD). Try removing the binarydocument reference (3bytes > version) and adding another (8MB version), should improve speed > drasticly due to dirty check > > -- > You received this message because you are subscribed to the Google Groups > "nhusers" 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/nhusers?hl=en. > > -- You received this message because you are subscribed to the Google Groups "nhusers" 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/nhusers?hl=en.
