[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-228?pag...
]
Hardy Ferentschik commented on HSEARCH-228:
-------------------------------------------
I would like to know how such a stress test should look like? Are we talking something
which should be runnable as part of the junit tests or something completely independent?
I could imagine using JMeter. We could start Hibernate Search as part of a simple web app.
There is no need for any fancy HTML output, just HTTP requests and XML/JSON responses.
Something that is easily parsable by JMeter. We can start the webapp either by a build
task or just use a standalone Jetty instance to sart the application under test.
The advantage of JMeter would be that we get a lot of the functionality we need for free -
concurrent access to the application (you can even run it truely distributed), error
detection by response parsing, reporting.
A disadvantage might be the addiotnal overhead with using a HTTP based test harness (even
thought this might actually be Hibernate Search's most commonly used use case).
Write a reliability test under stress
-------------------------------------
Key: HSEARCH-228
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-228
Project: Hibernate Search
Issue Type: Task
Reporter: Emmanuel Bernard
Fix For: 3.1.0.CR1
Write an app inserting, updating deleting concurrently
Also searching concurrently and make sure data is reliable during search
all that during stress conditions.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira