Archive for the ‘system_administration’ category

Benchmarking Solr

August 16, 2007

There was some discussion on the Vufind about moving from Tomcat to Jetty. I first wanted to see if it was possible to run this so I got the latest nightly build from Solr to see which packages were needed to run the server. I then grabbed the latest Jetty (6.1.5) since the version in Solr’s build was 6.1.3. I packaged the same files that were in Solr’s distribution and dropped Vufind’s schema and config file into Jetty and fired it up. Voila…it worked like a champ.

The thing I really wanted to know is if this Jetty version would perform in a similar fashion to Tomcat. What I did to test was set up two visualized servers on the same box. Each were set up with the exact same hardware (2GB RAM, 1 processor, bridged 1GB network, running Ubuntu 7.04 server). I also used the same Java tuning on both machines (“-server -Xmx1024m -Xms1024 -XX:+UseParallelGC -XX:+AggressiveOpts“). The only difference between the two was that one ran Tomcat and the other Jetty.

For the test, I indexed our library’s 1.8+ million catalog records on both machines which both chewed through the records in about 9 hours. To do the actual testing, I used JMeter to query both systems at the same time using a few scenarios that I thought might possibly be “real.”

In the first test, I sent 10 users with 100 queries for the book title “Flashman” to see what happened. I was pretty impressed with the results:

Server Samples Average Median Min Max
Jetty 1000 4ms 4ms 1ms 17ms
Tomcat 1000 3ms 4ms 0ms 28ms

You know, we might get a few more users than just 10 at a time, so I ramped it up to 100 users doing 10 queries. Again, there wasn’t much of a difference.

Server Samples Average Median Min Max
Jetty 1000 12ms 8ms 1ms 565ms
Tomcat 1000 9ms 7ms 1ms 530ms

Now to really ramp things up with 100 users doing 100 queries

Server Samples Average Median Min Max
Jetty 100000 9ms 6ms 1ms 2349ms
Tomcat 100000 9ms 6ms 1ms 1844ms

And, just for kicks, 1000 users with 10 queries

Server Samples Average Median Min Max
Jetty 10000 32ms 6ms 0ms 5643ms
Tomcat 10000 26ms 5ms 0ms 4295ms

With median results within a millisecond of each other, Andrew went ahead and swapped out Tomcat in favor for Jetty for its smaller footprint. I have to say that any time I’ve needed to do anything with JSP, I’ve opted to go with Tomcat. More because I know the name, but I think I’m going to keep Jetty on my list from now on! I want to take a closer look at their ANT and Eclipse Plugins!

SirsiDynix SuperConference – Day 2.5

February 22, 2007

I’m a bit more awake now so I will add a few more details for Day 2.

Tuesday was also the day of the System Administration Sharing Session.  There was a spirited discussion about the java workflows client.  Aspects of the use of the java client are enough to chill the soul of a system administrator.  I can’t find my notes on the session but here is what I recall:

  •  The java WorkFlows client uses Sun java runtime which is updated frequently.  Sometimes the upgrade breaks Workflows.  apparently Sun recently issued an update with major changes and didn’t tell anyone.  SirsiDynix is talking with Sun about finding a way to get a heads-up on major changes.
  • Where the C client handled printing with a dump to lpt, Java requires that printing go through Windows print drivers. Consequently, printing is slower.  Frequently it is much slower.  The latest print drivers don’t always work better.  Not good for Circulation activities.
  • Under MS Vist, java updates can only be installed by administrator.  This doesn’t mean someone in the administrator group, it must be administrator.  Yikes!  This means every staff station in the library will have to have java updated by someone from LIT .
  • Under Vista, Microsoft removed the way it handles help files.  While a C client will work on Vista, help won’t be available.  Yikes again!  The yellow question mark is our friend.  this means that new staff PCs delivered with Vista will require the java client.
  • The java client doesn’t support the “house” and binoculars” searches.  There is a multi-line Item Search and Display wizard.
  • The java client runs slow.

The last event of the day for me was the API Sharing Session and API After Hours.  Being the API forum Moderator I got to run these two events.  The Sharing Session is mostly administrative where we discuss enhancements, procedures, etc.  I gave some tips to the newly minted APIers.  I also made the plea that we get enhancements posted to the forum earlier so that we would have time for discussion prior to voting.  We also briefly discussed the value of an API wiki which everyone agreed was a fine idea if we can work out security details.  The System Administration wiki, which I co-manage, is proving successful and we feel that an API wiki will prove equally valuable.  I will work with SirsiDynix to explore this possibility.

The API  After Hours (aka API Mini-Summit) is more of a birds-of-a-feather session where the die-hards stick around and talk API.  Charles S. demonstrated several custom java reports written for his school system.  Pretty nifty.  Among other benefits, the reports give us good examples of coding particularly tricky parts of java client reports.

Shawn C. reprised a presentation she gave earlier but with more technical details that appealed to the APIers.  Shawn figured out how to do a variety of My Account activities outside of the OPAC including social software/networking tools such as tagging, book reviews, shared book lists, and RSS feeds.  She also demonstrated how she was able to created staff functions to give staff access to normally client-based activities.  Oooh! Bright & shiney.  Must have.finally, Joel H. and David B. volunteered to have questions thrown at them in an attempt to stump the experts.  There were not many questions (mostly because I neglected to tell anyone we were doing it) but they were not stumped.