Re: Untested Developer Code - lack of concurrency testing

From: Hemant K Chitale <>
Date: Fri, 15 May 2009 23:02:28 +0800
Message-Id: <>

This thread might be of interest :

At 11:11 PM Tuesday, kyle Hailey wrote:
>with one user and it runs fine and then gets put into production and
>only to hit a huge performance snafu. I'm putting together a demo
>on this kind of situation and was
>thinking of some examples. One example that came to mind is a Nesedt
>Loops join that hammers the root node of an index. Might work fine for
>one user, but when multiple users start running it, the query runs
>into cache buffers chains latch issues with the high concurrency
>access to the index's root block which might be resolved by doing a
>hash join or moving the lookup table to a hash cluster for
>example. Wondering if anyone else had good examples of developer code that
>worked fine with one user and broke in the multi user production

Hemant K Chitale

Received on Fri May 15 2009 - 10:02:28 CDT

Original text of this message