Thorsten Scherler (JIRA | 1 Jul 08:57 2008
Picon

[jira] Created: (FOR-1082) Concurrency testing of the locationmap throws errors

Concurrency testing of the locationmap throws errors
----------------------------------------------------

                 Key: FOR-1082
                 URL: https://issues.apache.org/jira/browse/FOR-1082
             Project: Forrest
          Issue Type: Bug
          Components: Locationmap
            Reporter: Thorsten Scherler

http://marc.info/?t=120180448900001&r=1&w=2
The problem that I encounter is that the locationmap is throwing an
error as soon as there are concurrent user. 

Try
<map:match pattern="test">
 <map:generate src="lm://transform.html.document"/>
<map:serialize  />
</map:match>

Doing some testing in my case I use jmeter with 250 threads and 100 loop
where the ramp-up time is 20. 

This provokes that the input module is requested on the startup with
more then one request. It seems that the requests are issued as fast
that the module seems to fail to finish to load the first time the
locationmap.

I changed 
public synchronized Object getAttribute(...)
(Continue reading)

Thorsten Scherler | 1 Jul 09:04 2008
Picon

Re: Concurrency testing of the locationmap throws errors

On Mon, 2008-06-30 at 09:14 -0400, Tim Williams wrote:
> On Mon, Jun 30, 2008 at 9:04 AM, Thorsten Scherler
> <thorsten.scherler.ext <at> juntadeandalucia.es> 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'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 does not change the situation.
> >
> >> Or, you could change the implementation from a HashMap
> >> to a ConcurrentHashMap and see if that helps.
> >
> > I changed
> > public synchronized Object getAttribute(...)
> > which seems to fix the problem.
> >
> > :)
> 
> I'm not sure that having getAttribute synchronized is good long term.
> Have you noticed a performance problems now?  Maybe create an issue to
> review this and figure out what the real culprit is in there?
> 

I will test the performance but in any case I think this problem needs
to fixed since concurrency bugs are really ugly to debug and having this
problem in a high traffic site is a complete showstopper. 
(Continue reading)

Thorsten Scherler | 1 Jul 09:25 2008
Picon

Re: Concurrency testing of the locationmap throws errors

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/sec and raise
to 5.1/sec.

salu2
--

-- 
Thorsten Scherler                                 thorsten.at.apache.org
Open Source Java                      consulting, training and solutions

Thorsten Scherler | 1 Jul 09:57 2008
Picon

Re: Concurrency testing of the locationmap throws errors

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 ruin the average.
> Since now we have 0% error the first hits are around 2.5/sec and raise
> to 5.1/sec.

BTW the site I am testing is http://juntadeandalucia.es/
(´╗┐dispatcher/cocoon-2.2 based) and now with 250 threads in parallel
doing each 100 request to different pages of the app brings me with lm
caching enabled a throughput of 52,5 /sec (sample size 8855 requests). 

salu2
--

-- 
Thorsten Scherler                                 thorsten.at.apache.org
Open Source Java                      consulting, training and solutions

Thorsten Scherler | 2 Jul 15:57 2008
Picon

Re: svn commit: r658178 - in /forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher: ./ src/documentation/content/xdocs/ src/documentation/content/xdocs/examples/ src/documentation/resources/structurer/url/examples/ src/documentati...

On Tue, 2008-05-20 at 09:37 +0000, gmcdonald <at> apache.org wrote:
> Author: gmcdonald
> Date: Tue May 20 02:37:51 2008
> New Revision: 658178
> 
> URL: http://svn.apache.org/viewvc?rev=658178&view=rev
> Log:
> Adding examples page and example
...
>     forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/forrest.properties
...
> Modified: forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/forrest.properties
> URL: http://svn.apache.org/viewvc/forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/forrest.properties?rev=658178&r1=658177&r2=658178&view=diff
> ==============================================================================
> ---
forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/forrest.properties (original)
> +++
forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/forrest.properties
Tue May 20 02:37:51 2008
>  <at>  <at>  -22,4 +22,4  <at>  <at> 
>  
>  # FIXME: FOR-785
>  forrest.validate.skinconf=false
> -project.required.plugins=org.apache.forrest.plugin.internal.dispatcher,org.apache.forrest.themes.core,org.apache.forrest.plugin.output.inputModule,org.apache.forrest.plugin.input.projectInfo,org.apache.forrest.plugin.output.pdf,org.apache.forrest.plugin.input.glossary
> +project.required.plugins=org.apache.forrest.plugin.internal.dispatcher,org.apache.forrest.themes.core,org.apache.forrest.plugin.output.inputModule,org.apache.forrest.plugin.input.projectInfo,org.apache.forrest.plugin.output.pdf,org.apache.forrest.plugin.input.glossary,org.apache.forrest.plugin.output.POD

Why did you added the POD plugin as required?

salu2
--

-- 
(Continue reading)

Gavin | 3 Jul 01:37 2008
Picon

RE: svn commit: r658178 - in/forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher:./ src/documentation/content/xdocs/src/documentation/content/xdocs/examples/src/documentation/resources/structurer/url/examples/ src/documentati...


> -----Original Message-----
> From: Thorsten Scherler [mailto:thorsten <at> apache.org]
> Sent: Wednesday, 2 July 2008 11:57 PM
> To: Forrest Developers List
> Subject: Re: svn commit: r658178 -
> in/forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dis
> patcher:./
> src/documentation/content/xdocs/src/documentation/content/xdocs/examples/s
> rc/documentation/resources/structurer/url/examples/ src/documentati...
> 
> On Tue, 2008-05-20 at 09:37 +0000, gmcdonald <at> apache.org wrote:
> > Author: gmcdonald
> > Date: Tue May 20 02:37:51 2008
> > New Revision: 658178
> >
> > URL: http://svn.apache.org/viewvc?rev=658178&view=rev
> > Log:
> > Adding examples page and example
> ...
> >
> forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispat
> cher/forrest.properties
> ...
> > Modified:
> forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispat
> cher/forrest.properties
> > URL:
> http://svn.apache.org/viewvc/forrest/trunk/whiteboard/plugins/org.apache.f
> orrest.plugin.internal.dispatcher/forrest.properties?rev=658178&r1=658177&
(Continue reading)

Sjur Moshagen | 3 Jul 11:26 2008
Picon

Re: svn commit: r673630 - /forrest/trunk/plugins/org.apache.forrest.plugin.output.pdf/resources/stylesheets/helper-commonElements.xsl

Hello,

Anybody able to help me? I thought that the following in document-to- 
fo.xsl:

   <xsl:variable
         name="sans-serif"
         select="'sans-serif'" />
   <xsl:variable
         name="serif"
         select="'serif'" />
   <xsl:variable
         name="monospace"
         select="'monospace'" />
...
   <xsl:include
         href="helper-commonElements.xsl" />

would automatically make the variables/params (I have tested both, no  
difference) available to helper-commonElements.xsl, but no. How come?

And sorry for the extra noise, I tested without restarting forrest,  
and it seemed to work fine. But stopping forrest, then forrest clean,  
then forrest run again displayed the problem. I assume that there's  
some caching things going on with pdf that makes the edit - reload  
cycle unreliable.

Best regards,
Sjur

(Continue reading)

Thorsten Scherler | 3 Jul 11:33 2008
Picon

Re: svn commit: r673630 - /forrest/trunk/plugins/org.apache.forrest.plugin.output.pdf/resources/stylesheets/helper-commonElements.xsl

On Thu, 2008-07-03 at 12:26 +0300, Sjur Moshagen wrote:
> Hello,
> 
> Anybody able to help me? I thought that the following in document-to- 
> fo.xsl:
> 
>    <xsl:variable
>          name="sans-serif"
>          select="'sans-serif'" />
>    <xsl:variable
>          name="serif"
>          select="'serif'" />
>    <xsl:variable
>          name="monospace"
>          select="'monospace'" />
> ...
>    <xsl:include
>          href="helper-commonElements.xsl" />

Hmm, not sure but did you try a xsl:import instead and not defining the
variables again. That should work.

salu2
--

-- 
Thorsten Scherler                                 thorsten.at.apache.org
Open Source Java                      consulting, training and solutions

Forrestbot | 3 Jul 12:08 2008
Picon

ForrestBot build for forrest-sample-2 FAILED

Automated build for forrest-sample-2 FAILED
Log attached.

----------
Forrestbot run ended at 03 July 10:08 AM
Using Forrest 0.9-dev
Forrestbot administrator: Forrest developers
----------

     [echo] 
          ....... Forrest render START 2008-07-03 10:07:08
          ... Rendering docs in /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2
        

check-java-version:
     [echo] This is apache-forrest-0.9-dev
     [echo] Using Java 1.4 from /usr/j2se/jre

init-props:
    [mkdir] Created dir: /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp

echo-settings:

check-skin:

init-proxy:

fetch-skins-descriptors:

fetch-skin:
(Continue reading)

Sjur Moshagen | 3 Jul 13:01 2008
Picon

Re: svn commit: r673630 - /forrest/trunk/plugins/org.apache.forrest.plugin.output.pdf/resources/stylesheets/helper-commonElements.xsl

Den 3. jul. 2008 kl. 12.33 skrev Thorsten Scherler:

> Hmm, not sure but did you try a xsl:import instead and not defining  
> the
> variables again. That should work.

Did try now - same result. To me this looks like something is blocking  
the include/import - this *ought to* work. I'm out of ideas at the  
moment.

Sjur


Gmane