Re: Concurrency testing of the locationmap throws errors

2008-07-01 Thread Thorsten Scherler
On Tue, 2008-07-01 at 09:25 +0200, Thorsten Scherler wrote: > On Tue, 2008-07-01 at 09:04 +0200, Thorsten Scherler wrote: > ... > > I will test the performance > ... > > Actually with the same test as before the performance is better. > > Mainly because before the first results are errors and r

Re: Concurrency testing of the locationmap throws errors

2008-07-01 Thread Thorsten Scherler
On Tue, 2008-07-01 at 09:04 +0200, Thorsten Scherler wrote: ... > I will test the performance ... Actually with the same test as before the performance is better. Mainly because before the first results are errors and ruin the average. Since now we have 0% error the first hits are around 2.5/se

Re: Concurrency testing of the locationmap throws errors

2008-07-01 Thread Thorsten Scherler
On Mon, 2008-06-30 at 09:14 -0400, Tim Williams wrote: > On Mon, Jun 30, 2008 at 9:04 AM, Thorsten Scherler > <[EMAIL PROTECTED]> wrote:svnc > > On Mon, 2008-06-30 at 08:34 -0400, Tim Williams wrote: > >> On Mon, Jun 30, 2008 at 8:12 AM, Thorsten Scherler > > ... > >> > >> I reckon in that case, it

Re: Concurrency testing of the locationmap throws errors

2008-06-30 Thread Tim Williams
On Mon, Jun 30, 2008 at 9:04 AM, Thorsten Scherler <[EMAIL PROTECTED]> wrote: > On Mon, 2008-06-30 at 08:34 -0400, Tim Williams wrote: >> On Mon, Jun 30, 2008 at 8:12 AM, Thorsten Scherler > ... >> >> I reckon in that case, it's either the caching or its deeper in the >> actual LM/nodes. You could

Re: Concurrency testing of the locationmap throws errors

2008-06-30 Thread Thorsten Scherler
On Mon, 2008-06-30 at 08:34 -0400, Tim Williams wrote: > On Mon, Jun 30, 2008 at 8:12 AM, Thorsten Scherler ... > > I reckon in that case, it's either the caching or its deeper in the > actual LM/nodes. You could try turning off caching completely and see > if it helps. Turning caching off doe

Re: Concurrency testing of the locationmap throws errors

2008-06-30 Thread Tim Williams
On Mon, Jun 30, 2008 at 8:12 AM, Thorsten Scherler <[EMAIL PROTECTED]> wrote: > On Mon, 2008-06-30 at 08:05 -0400, Tim Williams wrote: > ... >> > I am ATM playing around and it happens in >> > LocationMapModule.getLocationMap() but I am not sure how I can prevent >> > it. >> >> Try making the entir

Re: Concurrency testing of the locationmap throws errors

2008-06-30 Thread Thorsten Scherler
On Mon, 2008-06-30 at 08:05 -0400, Tim Williams wrote: ... > > I am ATM playing around and it happens in > > LocationMapModule.getLocationMap() but I am not sure how I can prevent > > it. > > Try making the entire method synchronized instead of just the blocks. > This may not be the end solution b

Re: Concurrency testing of the locationmap throws errors

2008-06-30 Thread Tim Williams
On Mon, Jun 30, 2008 at 7:46 AM, Thorsten Scherler <[EMAIL PROTECTED]> wrote: > On Thu, 2008-01-31 at 15:16 -0500, Tim Williams wrote: >> On Jan 31, 2008 1:19 PM, Thorsten Scherler >> <[EMAIL PROTECTED]> wrote: >> > Hi all, >> > >> > I am ATM testing the dispatcher with jmeter and concurrent user.

Re: Concurrency testing of the locationmap throws errors

2008-06-30 Thread Thorsten Scherler
On Thu, 2008-01-31 at 15:16 -0500, Tim Williams wrote: > On Jan 31, 2008 1:19 PM, Thorsten Scherler > <[EMAIL PROTECTED]> wrote: > > Hi all, > > > > I am ATM testing the dispatcher with jmeter and concurrent user. > > > > The problem that I encounter is that the locationmap is throwing an > > error

Re: Concurrency testing of the locationmap throws errors

2008-01-31 Thread Tim Williams
On Jan 31, 2008 1:19 PM, Thorsten Scherler <[EMAIL PROTECTED]> wrote: > Hi all, > > I am ATM testing the dispatcher with jmeter and concurrent user. > > The problem that I encounter is that the locationmap is throwing an > error as soon as there are concurrent user. :( > > I have no clue ATM why th