Re: debugging slowness
Right. ssh -X to your EC2 box, run jps to get your java process PID, and then run jconsole PID and wait for jconsole to show up (tends to be slow when done remotely like this). jtop is also your friend. Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch - Original Message From: Ryan McKinley [EMAIL PROTECTED] To: solr-user@lucene.apache.org Sent: Thursday, December 20, 2007 11:26:50 AM Subject: Re: debugging slowness Can't run jconsole, no X at the moment, if need be I'll install it though... You should be able to connect jconsole to a remote process (no need for X on the server) check: http://java.sun.com/j2se/1.5.0/docs/guide/management/ http://www.componative2.com/content/controller/developer/insights/jconsole1 ryan
Re: debugging slowness
Brian (moving to solr-user), Sounds like GC to me. That is, the JVM not having large enough heap. Run jconsole and you'll quickly see if this guess is correct or not (kill -QUIT is also your friend, believe it or not). We recently had somebody who had a nice little Solr spellchecker instance running, but after awhile it would stop responding. We looked at the command-line used to invoke the servlet container and didn't see -Xmx. :) Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch - Original Message From: Brian Whitman [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, December 19, 2007 9:23:01 AM Subject: debugging slowness We've got periods where direct solr queries take 35s; on resin reboot they go back to taking 500ms. This is on a 16GB ram 4-core server. We want to debug this but don't know where to start. Is there some sample- type command we can run during queries to figure out where Solr/Lucene is spending its time (ala MySQL's slow query log)?
Re: debugging slowness
On Dec 20, 2007, at 11:02 AM, Otis Gospodnetic wrote: Sounds like GC to me. That is, the JVM not having large enough heap. Run jconsole and you'll quickly see if this guess is correct or not (kill -QUIT is also your friend, believe it or not). We recently had somebody who had a nice little Solr spellchecker instance running, but after awhile it would stop responding. We looked at the command-line used to invoke the servlet container and didn't see -Xmx. :)] I'm giving resin args=-J-mx1m -J-ms5000m (this is a amazon xtra- large instance w/ 16GB), it's using it PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 2738 root 18 0 10.4g 9.9g 9756 S 231 66.0 48:07.66 java After a restart yesterday and normal operation we haven't seen the problem creep back in yet. I might get my perl on to graph the query time and see if it's steadily increasing. Can't run jconsole, no X at the moment, if need be I'll install it though...
Re: debugging slowness
Can't run jconsole, no X at the moment, if need be I'll install it though... You should be able to connect jconsole to a remote process (no need for X on the server) check: http://java.sun.com/j2se/1.5.0/docs/guide/management/ http://www.componative2.com/content/controller/developer/insights/jconsole1 ryan
