Bugzilla – Full Text Bug Listing
| Summary: | Regression: Initializing search indices takes forever | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Ortwin Glück <odi> |
| Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 4.6 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | stalebug | ||
|
Description
Ortwin Glück
The workload is only CPU bound (1 CPU maxed out). Disk (SSD RAID-0) and memory are no problem. GC activity is negligible. ATOP - localhost 2017/01/31 11:29:41 ------------- 10s elapsed PRC | sys 0.46s | user 10.04s | #proc 233 | #tslpi 510 | #tslpu 0 | #zombie 0 | #exit 0 | CPU | sys 4% | user 99% | irq 1% | idle 686% | wait 11% | curf 3.23GHz | curscal 87% | cpu | sys 1% | user 27% | irq 0% | idle 68% | cpu000 w 4% | curf 2.88GHz | curscal 77% | cpu | sys 1% | user 23% | irq 0% | idle 73% | cpu002 w 3% | curf 2.87GHz | curscal 77% | cpu | sys 0% | user 17% | irq 0% | idle 82% | cpu001 w 1% | curf 3.45GHz | curscal 93% | cpu | sys 1% | user 15% | irq 0% | idle 82% | cpu003 w 2% | curf 3.68GHz | curscal 99% | cpu | sys 1% | user 8% | irq 0% | idle 91% | cpu004 w 1% | curf 2.95GHz | curscal 79% | cpu | sys 1% | user 3% | irq 0% | idle 96% | cpu006 w 0% | curf 2.87GHz | curscal 77% | cpu | sys 1% | user 3% | irq 0% | idle 97% | cpu007 w 0% | curf 3.42GHz | curscal 92% | cpu | sys 0% | user 3% | irq 0% | idle 97% | cpu005 w 0% | curf 3.70GHz | curscal 99% | CPL | avg1 1.17 | avg5 1.33 | avg15 1.27 | csw 33382 | intr 18510 | | numcpu 8 | MEM | tot 15.5G | free 161.0M | cache 9.3G | buff 1.0G | slab 1.8G | vmbal 0.0M | hptot 0.0M | SWP | tot 0.0M | free 0.0M | | | | vmcom 4.9G | vmlim 15.5G | PAG | scan 18038 | steal 18038 | stall 0 | | | swin 0 | swout 0 | MDD | md127 | busy 0% | read 10384 | write 111 | MBr/s 7.2 | MBw/s 1.8 | avio 0.00 ms | DSK | sda | busy 7% | read 5242 | write 19 | MBr/s 3.6 | MBw/s 0.9 | avio 0.13 ms | DSK | sdb | busy 6% | read 5205 | write 20 | MBr/s 3.5 | MBw/s 0.9 | avio 0.12 ms | NET | transport | tcpi 28 | tcpo 29 | udpi 15 | udpo 0 | tcpao 0 | tcppo 0 | NET | network | ipi 69 | ipo 29 | ipfrw 0 | deliv 43 | icmpi 0 | icmpo 0 | NET | eth0 0% | sp 1000 Mbps | pcki 69 | pcko 10 | si 20 Kbps | so 0 Kbps | erro 0 | NET | lo ---- | sp 0 Mbps | pcki 24 | pcko 24 | si 3 Kbps | so 3 Kbps | erro 0 | PID TID RUID EUID THR SYSCPU USRCPU VGROW RGROW RDDSK WRDSK ST EXC S CPUNR CPU CMD 1/1 13361 - oglueck oglueck 66 0.34s 9.89s -4100K -10.1M 73300K 18488K -- - S 7 103% java The indexing finally completed in about 30 minutes. Looks like the performance is not linear. So it may be that a long list of still to index files is traveresed often or something like that. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |