umit / solrmeter Goto Github PK

Modify SolrJ Server configuration attributes from UI.

It would be good to be abble to specify an external properties file (external 
to the jar file). That way it would be easier to change properties.

Prevent the FileNotFoundException when the test files are not found. It should 
show some message to the user instead.

Would be nice that solrmeter allows to specify the time to run the tests...

For example, i would like that the tests runs only two hours and stop or set an 
start time and end time.
Probably a notification of finish would be ok too.

On Actual Version, all settings accepts plain text from the UI. This is not 
good becouse some values are number, booleans or some other type.
It would be good to have type-specific panels for number, booleans and 
customized combos (for example, for the facet method).

After running solrmeter test for the first time some files are generated and 
not deleted on the root of the project:
histogram.csv
queryTime.csv
SolrMeterConfigurationTestCase-testExport

Add an executor to delete docs from index.

It would be good to visualize the Solr query handler stats as the one shown on 
the "stats" page of solr admin with a chart on the UI. This way, users will be 
able to see how they change without needing to refresh the page every time.

Add the functionality to select wich statistics you want to see on the UI. This 
will become really important if the number of statistics grows.

It would be good to be able to override any property that's on the 
"solrmeter.properties" file with an init parameter. It would be something like:

java -jar solrmeter.jar -Pproperty.name=propertyValue

That way, it will is not necesary to open the jar file for updating a single 
property.

Allow to extract data sets (queries and documents for update/insert) from a 
data base. Today this data is being extracted from text files.

It's really anoying to use the queries per minute/updates per minute visual 
component when you have to increment/decrement more than 1000. It would be good 
to have a more usefull component.

Add the functionality to replace the default configuration with the actual 
configuration.

Users should be able to change the "fields.txt" file, necesary for faceting 
from the user interface.

Extract Data for updates/inserts/deletes from an existing Lucene index.

Allow to change the number of ranges and limits of each one on the Cake chart.

Obtain index schama information from the schema.xml file of Solr configuration. 
This should replace the actual "field.txt" file that is use for faceting.

Add the functionality to Query Solr, the same way the solr admin does.

It would be good to be able to specify the parameter separator for the "extra 
params", either the static extra params or the random ones. Now it uses the "," 
for the static and "&" for the random. Unify.

Similiar options can be group together in setting dialog, e.g. use facet & 
facet method can be grouped together.

Get a logo for google code and for the google group

The code is growing and having dependency injection is being more and more 
important.
This is important to improve code quality but mostly to allow customizations to 
be pluggable on a simple way.

Add the functionality to restart tests

Add java web start capabilities to run solrmeter from the project webpage

FullQueryStatistic sometimes show -1 in the las ten minutes time average

When tests are long, charts get dificult to read.

Allow to set facet fields of query from UI. Facet fields could also be choosed 
randomly.

Show Cache statistics(the ones shown on the Solr admin page) on a lines chart.

Send ping and some queries and monitor responses to determine solr availability

It should be possible to add a Solr Log File instead of a straight queries 
file. 

Parametrize Solr Server configuration from UI.

Show the "debug query" information of a query when double clicking on a query 
on the query log. 
The information should be well presented.

It would be good to be able set up diferent configuration parameters for 
diferent solr servers (for example, one for queries and one for updates)

On this version, the user can only specify the number of queries (or updates) 
per minute. This is good for cases when the queries expected are not too hi, 
but its a problem when queries expected are many (500 qps is translated to 
30,000 qpm). User should be able to specify the number of queries and the unit 
of time (second or minute).

Refactor code to allow statistics to be added as plugins.

Separata Update executor into an "Insert Executor" that adds only new docs to 
Solr and an "Update executor" that only updates existing docs.

Persist and load test runs results to compare one to each other to do 
performance and behavioural analysis

Investigate JMeter integration

Sometimes the number of queries per minute specified is not achived by one 
SolrMeter instance. It would be good to be able to see the real number of 
queries per second (oer minute) that are really being executed.

I would be good to have example files for running solrmeter with the "example" 
solr implementation that comes with the standard distribution.

Refactor "refresh" of test properties. Actual code doesn't allow to make 
changes during a test.

That way, solrmeter could also be "lucenemeter".

There is no alert when the target solr server is down when running queries or 
updates. The only way is to run the test and then check the error log tab.
It would be good that solrmeter shows an alert when the target solr server is 
down.

With all the information solrmeter gathers from Solr configuration and 
statistics, SolrMeter could recomend the user to perform changes on Solr 
configuration.
For example, if autowarm is taking too long and commits are performed in a 
relatively short interval, SolrMeter could recomend to low the autowarm time by 
putting lower values on "autowarm" attributes of cache configuration.
There could be many of this kind of rules and they could be implemented with 
some business rule management system like drools.

The idea is to make UI easyer to read.

Help menu item with a simple tutorial help page.

Actual version, executors execute N queries (or updates) per minute randomly 
distributed. An improvement would be to allow also execute N queries per minute 
uniformely distributed.

For example:
Setting 60 queries per minute on actual version could execute 50 queries during 
the first 10 seconds, and 10 queries during the other 50 seconds.
Setting 60 queries per minute on an uniformely distributed executor would 
execute one query per second.

Add the functionality to ping all Solr Servers. This is usefull to prove server 
status before starting a test.

What steps will reproduce the problem?
1. Executing queries at (180 q/min)
2. Wait for a Exception
3. See the log

What is the expected output? What do you see instead?
In the log should appear the exception and the stack trace

When looking the log, i can't see the exception with the stack trace.
I don't see any info about exceptions.

What version of the product are you using? On what operating system?
solrmeter-0.1.1-jar-with-dependencies.jar downloaded from the Project Home
Running in Windows XP SP3 (OEM Version i think).
java version "1.6.0_16"
Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
Java HotSpot(TM) Client VM (build 14.2-b01, mixed mode, sharing)


Note:
After this exception the timeline chart stops updating, the rest of the panels 
works well.

It would be good to be able to see Solr configuration information (that is 
published on request handlers) from solrmeter.