Also note that if you've fired some warmup queries at one machine but not the other that'll skew your results...
Erick On Wed, Oct 6, 2010 at 7:22 AM, Sergey <semy...@yandex.ru> wrote: > Thanks, I'll give it a try. > > 06.10.10, 14:47, "Toke Eskildsen" <t...@statsbiblioteket.dk>: > > > On Wed, 2010-10-06 at 12:22 +0200, Sergey wrote: > > > When running application on Windows XP 32 bit machine the search time > is 0.5 second. JVM is IBM Java 5 for 32 bit. > > > But when running the same application on much more powerfull Windows > Server 2007 64 bit machine the search time is 3 seconds. JVM is IBM Java 5 > for 64 bit. > > > > If your memory allocation (-Xmx) is the same, the 64 bit machine will > > have less available heap due to the 64 bit pointers. This could result > > in excessive garbage collection. Try increasing the memory allocation > > for the 64 bit machine with 50% or more. > > > > Besides that, there should be no significant difference and you're left > > with profiling. I recommend Process Explorer > > http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx > > for general system and single process load inspection. I/O is often the > > sinner, så check read and write calls. > > > > Switching to the Java part, try using visualvm > > https://visualvm.dev.java.net/ > > with the Visual GC-plugin to see where the time is spend. > > > > - Toke Eskildsen > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > > For additional commands, e-mail: java-user-h...@lucene.apache.org > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > >
