You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stanbol.apache.org by Rupert Westenthaler <ru...@gmail.com> on 2012/07/03 16:46:53 UTC
Stanbol Enhancer Stress Test Tool
Hi all,
while working on STANBOL-668 and STANBOL-669 I have started to
implement an integration-test that is capable of sending multiple
concurrent enhancement requests to the Stanbol Enhancer. Because I
found this tool very useful I have spent some more effort to make it
also useful for Stanbol users that want to test their Stanbol
server/configuration and Stanbol developers that want e.g. test a
newly implemented Enhancement Engine.
For more information see the Documentation [1] and this a Blog post
about the Tool [2].
Happy testing!
Rupert
[1] http://incubator.apache.org/stanbol/docs/trunk/utils/enhancerstresstest
[2] http://blog.iks-project.eu/apache-stanbol-stress-test-tool/
--
| Rupert Westenthaler rupert.westenthaler@gmail.com
| Bodenlehenstraße 11 ++43-699-11108907
| A-5500 Bischofshofen
Re: Stanbol Enhancer Stress Test Tool
Posted by Anuj Kumar <an...@gmail.com>.
Ok. Thanks.
On Thu, Jul 5, 2012 at 3:43 PM, Rupert Westenthaler <
rupert.westenthaler@gmail.com> wrote:
> Hi,
>
> Errors like that are the result of STANBOL-668 and the change of this
> error to happen is greatly increased of you run into STANBOL-669. You
> can also check if you are affected by STANBOL-669 if Stanbol uses up
> CPU time even if there are no enhancement requests.
>
> It is not a surprise that this happens as this tool was initially
> implemented to replicate and fixe those two issues.
>
> best
> Rupert
>
>
> On Thu, Jul 5, 2012 at 10:03 AM, Anuj Kumar <an...@gmail.com> wrote:
> > Thanks Rupert. This is useful. I just ran it with my healthcare enhancer-
> >
> > 68881 [main] INFO org.apache.stanbol.enhancer.it.MultiThreadedTest -
> > Enhancement Engines
> > 68882 [main] INFO org.apache.stanbol.enhancer.it.MultiThreadedTest -
> > dbpediaLinking: max: 1028ms | min: 0ms | avr: 65ms over 498 requests
> > 68882 [main] INFO org.apache.stanbol.enhancer.it.MultiThreadedTest -
> > entityhubExtraction: max: 513ms | min: 1ms | avr: 42ms over 498 requests
> > 68882 [main] INFO org.apache.stanbol.enhancer.it.MultiThreadedTest -
> > *formcept-healthcare: max: 954ms | min: 28ms | avr: 67ms over 498
> > requests
> > *
> > 68883 [main] INFO org.apache.stanbol.enhancer.it.MultiThreadedTest -
> > langid: max: 470ms | min: 3ms | avr: 12ms over 498 requests
> > 68883 [main] INFO org.apache.stanbol.enhancer.it.MultiThreadedTest -
> ner:
> > max: 816ms | min: 0ms | avr: 34ms over 498 requests
> > 68883 [main] INFO org.apache.stanbol.enhancer.it.MultiThreadedTest -
> > tika: max: 26ms | min: 0ms | avr: 1ms over 498 requests
> >
> > I also got an error message-
> >
> > [Content-Type: text/html; charset=iso-8859-1, Cache-Control:
> > must-revalidate,no-cache,no-store, Content-Length: 11373, Server:
> > Jetty(6.1.x)], HTTP/1.1 500 Enhancement Chain failed because of required
> > Engine 'dbpediaLinking' failed with Message: Unable to process
> ContentItem
> > '<urn:content-item-sha1-85c1eddee158cd4150c3ea035bd038988854434a>' with
> > Enhancement Engine 'dbpediaLinking' because the engine was unable to
> > process the content (Engine class:
> >
> org.apache.stanbol.enhancer.engines.entitytagging.impl.NamedEntityTaggingEngine)(Reason:
> > Unknown prefix geo (parsed from field geo:long)!)! [Content-Type:
> > text/html; charset=iso-8859-1, Cache-Control:
> > must-revalidate,no-cache,no-store, Content-Length: 12076, Server:
> > Jetty(6.1.x)]]/5 failed
> >
> > Please note that I ran the tests against my running instance that is not
> on
> > the latest build. Is that the issue?
> >
> > Thanks,
> > Anuj
> >
> > On Tue, Jul 3, 2012 at 8:16 PM, Rupert Westenthaler <
> > rupert.westenthaler@gmail.com> wrote:
> >
> >> Hi all,
> >>
> >> while working on STANBOL-668 and STANBOL-669 I have started to
> >> implement an integration-test that is capable of sending multiple
> >> concurrent enhancement requests to the Stanbol Enhancer. Because I
> >> found this tool very useful I have spent some more effort to make it
> >> also useful for Stanbol users that want to test their Stanbol
> >> server/configuration and Stanbol developers that want e.g. test a
> >> newly implemented Enhancement Engine.
> >>
> >> For more information see the Documentation [1] and this a Blog post
> >> about the Tool [2].
> >>
> >> Happy testing!
> >> Rupert
> >>
> >> [1]
> >> http://incubator.apache.org/stanbol/docs/trunk/utils/enhancerstresstest
> >> [2] http://blog.iks-project.eu/apache-stanbol-stress-test-tool/
> >>
> >> --
> >> | Rupert Westenthaler rupert.westenthaler@gmail.com
> >> | Bodenlehenstraße 11 ++43-699-11108907
> >> | A-5500 Bischofshofen
> >>
>
>
>
> --
> | Rupert Westenthaler rupert.westenthaler@gmail.com
> | Bodenlehenstraße 11 ++43-699-11108907
> | A-5500 Bischofshofen
>
Re: Stanbol Enhancer Stress Test Tool
Posted by Rupert Westenthaler <ru...@gmail.com>.
Hi,
Errors like that are the result of STANBOL-668 and the change of this
error to happen is greatly increased of you run into STANBOL-669. You
can also check if you are affected by STANBOL-669 if Stanbol uses up
CPU time even if there are no enhancement requests.
It is not a surprise that this happens as this tool was initially
implemented to replicate and fixe those two issues.
best
Rupert
On Thu, Jul 5, 2012 at 10:03 AM, Anuj Kumar <an...@gmail.com> wrote:
> Thanks Rupert. This is useful. I just ran it with my healthcare enhancer-
>
> 68881 [main] INFO org.apache.stanbol.enhancer.it.MultiThreadedTest -
> Enhancement Engines
> 68882 [main] INFO org.apache.stanbol.enhancer.it.MultiThreadedTest -
> dbpediaLinking: max: 1028ms | min: 0ms | avr: 65ms over 498 requests
> 68882 [main] INFO org.apache.stanbol.enhancer.it.MultiThreadedTest -
> entityhubExtraction: max: 513ms | min: 1ms | avr: 42ms over 498 requests
> 68882 [main] INFO org.apache.stanbol.enhancer.it.MultiThreadedTest -
> *formcept-healthcare: max: 954ms | min: 28ms | avr: 67ms over 498
> requests
> *
> 68883 [main] INFO org.apache.stanbol.enhancer.it.MultiThreadedTest -
> langid: max: 470ms | min: 3ms | avr: 12ms over 498 requests
> 68883 [main] INFO org.apache.stanbol.enhancer.it.MultiThreadedTest - ner:
> max: 816ms | min: 0ms | avr: 34ms over 498 requests
> 68883 [main] INFO org.apache.stanbol.enhancer.it.MultiThreadedTest -
> tika: max: 26ms | min: 0ms | avr: 1ms over 498 requests
>
> I also got an error message-
>
> [Content-Type: text/html; charset=iso-8859-1, Cache-Control:
> must-revalidate,no-cache,no-store, Content-Length: 11373, Server:
> Jetty(6.1.x)], HTTP/1.1 500 Enhancement Chain failed because of required
> Engine 'dbpediaLinking' failed with Message: Unable to process ContentItem
> '<urn:content-item-sha1-85c1eddee158cd4150c3ea035bd038988854434a>' with
> Enhancement Engine 'dbpediaLinking' because the engine was unable to
> process the content (Engine class:
> org.apache.stanbol.enhancer.engines.entitytagging.impl.NamedEntityTaggingEngine)(Reason:
> Unknown prefix geo (parsed from field geo:long)!)! [Content-Type:
> text/html; charset=iso-8859-1, Cache-Control:
> must-revalidate,no-cache,no-store, Content-Length: 12076, Server:
> Jetty(6.1.x)]]/5 failed
>
> Please note that I ran the tests against my running instance that is not on
> the latest build. Is that the issue?
>
> Thanks,
> Anuj
>
> On Tue, Jul 3, 2012 at 8:16 PM, Rupert Westenthaler <
> rupert.westenthaler@gmail.com> wrote:
>
>> Hi all,
>>
>> while working on STANBOL-668 and STANBOL-669 I have started to
>> implement an integration-test that is capable of sending multiple
>> concurrent enhancement requests to the Stanbol Enhancer. Because I
>> found this tool very useful I have spent some more effort to make it
>> also useful for Stanbol users that want to test their Stanbol
>> server/configuration and Stanbol developers that want e.g. test a
>> newly implemented Enhancement Engine.
>>
>> For more information see the Documentation [1] and this a Blog post
>> about the Tool [2].
>>
>> Happy testing!
>> Rupert
>>
>> [1]
>> http://incubator.apache.org/stanbol/docs/trunk/utils/enhancerstresstest
>> [2] http://blog.iks-project.eu/apache-stanbol-stress-test-tool/
>>
>> --
>> | Rupert Westenthaler rupert.westenthaler@gmail.com
>> | Bodenlehenstraße 11 ++43-699-11108907
>> | A-5500 Bischofshofen
>>
--
| Rupert Westenthaler rupert.westenthaler@gmail.com
| Bodenlehenstraße 11 ++43-699-11108907
| A-5500 Bischofshofen
Re: Stanbol Enhancer Stress Test Tool
Posted by Anuj Kumar <an...@gmail.com>.
Thanks Rupert. This is useful. I just ran it with my healthcare enhancer-
68881 [main] INFO org.apache.stanbol.enhancer.it.MultiThreadedTest -
Enhancement Engines
68882 [main] INFO org.apache.stanbol.enhancer.it.MultiThreadedTest -
dbpediaLinking: max: 1028ms | min: 0ms | avr: 65ms over 498 requests
68882 [main] INFO org.apache.stanbol.enhancer.it.MultiThreadedTest -
entityhubExtraction: max: 513ms | min: 1ms | avr: 42ms over 498 requests
68882 [main] INFO org.apache.stanbol.enhancer.it.MultiThreadedTest -
*formcept-healthcare: max: 954ms | min: 28ms | avr: 67ms over 498
requests
*
68883 [main] INFO org.apache.stanbol.enhancer.it.MultiThreadedTest -
langid: max: 470ms | min: 3ms | avr: 12ms over 498 requests
68883 [main] INFO org.apache.stanbol.enhancer.it.MultiThreadedTest - ner:
max: 816ms | min: 0ms | avr: 34ms over 498 requests
68883 [main] INFO org.apache.stanbol.enhancer.it.MultiThreadedTest -
tika: max: 26ms | min: 0ms | avr: 1ms over 498 requests
I also got an error message-
[Content-Type: text/html; charset=iso-8859-1, Cache-Control:
must-revalidate,no-cache,no-store, Content-Length: 11373, Server:
Jetty(6.1.x)], HTTP/1.1 500 Enhancement Chain failed because of required
Engine 'dbpediaLinking' failed with Message: Unable to process ContentItem
'<urn:content-item-sha1-85c1eddee158cd4150c3ea035bd038988854434a>' with
Enhancement Engine 'dbpediaLinking' because the engine was unable to
process the content (Engine class:
org.apache.stanbol.enhancer.engines.entitytagging.impl.NamedEntityTaggingEngine)(Reason:
Unknown prefix geo (parsed from field geo:long)!)! [Content-Type:
text/html; charset=iso-8859-1, Cache-Control:
must-revalidate,no-cache,no-store, Content-Length: 12076, Server:
Jetty(6.1.x)]]/5 failed
Please note that I ran the tests against my running instance that is not on
the latest build. Is that the issue?
Thanks,
Anuj
On Tue, Jul 3, 2012 at 8:16 PM, Rupert Westenthaler <
rupert.westenthaler@gmail.com> wrote:
> Hi all,
>
> while working on STANBOL-668 and STANBOL-669 I have started to
> implement an integration-test that is capable of sending multiple
> concurrent enhancement requests to the Stanbol Enhancer. Because I
> found this tool very useful I have spent some more effort to make it
> also useful for Stanbol users that want to test their Stanbol
> server/configuration and Stanbol developers that want e.g. test a
> newly implemented Enhancement Engine.
>
> For more information see the Documentation [1] and this a Blog post
> about the Tool [2].
>
> Happy testing!
> Rupert
>
> [1]
> http://incubator.apache.org/stanbol/docs/trunk/utils/enhancerstresstest
> [2] http://blog.iks-project.eu/apache-stanbol-stress-test-tool/
>
> --
> | Rupert Westenthaler rupert.westenthaler@gmail.com
> | Bodenlehenstraße 11 ++43-699-11108907
> | A-5500 Bischofshofen
>