search for: 1m59s

...mplete+0x19f bufdone_finish() at bufdone_finish+0x2d bufdone() at bufdone+0x6c g_io_schedule_up() at g_io_schedule_up+0xce g_up_procbody() at g_up_procbody+0x72 fork_exit() at fork_exit+0x135 fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffff85d8a93bb0, rbp = 0 --- Uptime: 1m59s Dumping 1219 out of 24477 MB:panic: msleep cpuid = 26 Uptime: 1m59s panic: msleep cpuid = 26 Uptime: 1m59s panic: msleep cpuid = 26 Uptime: 1m59s panic: msleep cpuid = 26 Uptime: 1m59s panic: msleep cpuid = 26 Uptime: 1m59s panic: msleep cpuid = 26 Uptime: 1m59s panic: msleep cpuid = 26 Uptime: 1m5...

...nc'ing my directory tree (100 directories each containing 1000 files) I see some strange results: All of these machines are on their own network segment (100t) in our QA lab Solaris->Solaris - time taken: 11m32s Solaris->RH Linux 7.2 - time taken: 206s RH Linux->Rn Linux - time taken 1m59s In each instance I have rsync running as a server on the target machine (Linux in each case). I just can't explain why the performance is just so AMAZING on Linux. Any ideas? Thanks Dave Dave North Solutions Engineering SIGNIANT Inc. www.signiant.com Phone: 613-599-2158...

...ectory: -------------- Xapian 1.2.22 Index size 615 MB time: real 2m20s user 7m57s sys 1m34s Approximately 2mn of CPU time are spent in the actual Xapian thread (which gets xapian::document as input and processes them into the index). Xapian 1.3.5 Index size 794MB time: real 3m47s user 7m14s sys 1m59s Approximately 2m40s of CPU time are spent in the Xapian thread. Indexing performance, interpretation: ------------------------------------ On the PDF directory, the performance of the Xapian thread is masked by the processing of the PDF input. The CPU utilization is good (CPU time/clock time is...