SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
SI - Site Forums : Silicon Investor - Legacy Interface Discussion (2004-2011)

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: SI Dave who wrote (2253)10/13/2004 1:21:56 PM
From: SI Bob   of 6035
 
I'm running a trace right now that's showing all the relevant data for public message inserts.

When I started it, I was seeing minimum duration times of 13ms and some maximums in excess of a second!

I added a couple of indexes that I think should help and so far I'm seeing a lot more zero-duration runs and a few as high as 46ms.

Speeding it up isn't going to be the only solution. But it helps.

There's usually well over a one-second gap between inserts, but I just saw one that started right at the previous one's end-time. To the millisecond. What I'm looking for, though, is whether any are starting before the previous one has finished. That would likely cause some problems. It may be that due to the inner workings of how SQL Server locks tables, an instance of message-insertion can't start until the previous one has finished. Don't know yet.
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext