#9256 closed enhancement (fixed)
Test "Unconnected Ways" is slow
Reported by: | mkoniecz | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core validator | Version: | |
Keywords: | performance unconnected_way | Cc: |
Description (last modified by )
On large data (141 MB map of the city obtained via http://overpass-api.de/api/interpreter?data=(node(50,19.78,50.11,20.09);<;);out meta; ) it is running for hours, without visible change. I am not sure is it completely frozen, performing task that cannot be speed up or is it using naive algorithm.
I request that Unconnected Ways test will be speed up and/or progress bar for individual tests of validator will be added (so it is possible to estimate whatever validator will run this test for next hour or the next century or is it completely frozen).
Answer to question why I want to run validator test on the entire city:
- I wanted to check whatever number of things detected by validator is growing or shrinking over time
- I fixed problems in some areas and I prefer to not waste time on downloading small parts of city via limited data downloader in JSOM and discovering that in this area everything is fixed
- I prefer to fix one group of things in one run
Attachments (0)
Change History (8)
comment:1 by , 11 years ago
Keywords: | performance added |
---|
comment:2 by , 11 years ago
Keywords: | unconnected_way added |
---|
comment:3 by , 11 years ago
Description: | modified (diff) |
---|---|
Summary: | Test "Starting Unconnected Ways" is slow → Test "Unconnected Ways" is slow |
comment:4 by , 11 years ago
comment:5 by , 11 years ago
Crash happened on running validator, data file was 147 MB and was obtained (the same bounding box as previously) from overpass API. Reported as #9731.
comment:6 by , 11 years ago
Interface is incredibly laggy, but validator runs within hour what is acceptable for 147 MB of data. Thanks for improvements! It is at least 10 times faster!
comment:7 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:8 by , 11 years ago
And - it is still really slow (over 16 minutes on this dataset) and making it faster would be great.
We made some performance improvements to validator since the creation of this ticket, can you check if it's better?