Re: Untested Developer Code - lack of concurrency testing

From: Chen Shapira <>
Date: Tue, 12 May 2009 08:47:49 -0700
Message-ID: <>

Hi Kyle,

I wrote a paper with few examples of these kinds of issues:

The scripts that are mentioned in the paper can be downloaded here:


Chen Shapira

On Tue, May 12, 2009 at 8:11 AM, 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
> environment.

Received on Tue May 12 2009 - 10:47:49 CDT

Original text of this message