On Sonntag, 29. Juni 2008, qaz zaq wrote: > indexes which usually take less then 16ms. However, everytime afer some > heavy disk operations (such as copy 1G size of a file into that disk) , > the document retrieval slows down to couple seconds immediately, > even well after this disk operation being finished for a long time.
Is this copy operation initiated by your java code and does it require a lot of RAM? If so, this could be caused by the JVM garbage collection. There are options to start the JVM so it prints out garbage collection progress information. Also, are you sure the copy operation is finished? Maybe data is still in the cache of the operating system and the disk is still busy writing it? Regards Daniel -- http://www.danielnaber.de --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
