Opened 11 years ago

Closed 7 years ago

#2526 closed defect (wontfix)

value of "MaxTilesetComplexity" changes dynamicaly during "perl loop"

Reported by: iknopf Owned by: osm@…
Priority: major Milestone:
Component: tilesathome Version:
Keywords: Cc:


In "tilesAtHome.conf" I set "MaxTilesetComplexity? = 25000000". I think, this should be o.k., I have loads of RAM.

Running the tiles@home client some hours, I get the following output:

[#161 100% ] Tile of complexity 566827 took us 261 seconds to render
[#161 100% ] Suggested complexity is currently: 5328518
[#161 100% ] Waiting for previous upload process to finish (this can take a while)
[#162 100% ] Ignoring too complex tile (12,2143,1400, 7620973 > 5328518)
[#162 100% ] Putting job (12,2143,1400) back due to 'TooComplex'

So this means, after 161 iterations the initial value of MaxTilesetComplexity? has been decreased to 5328518. And this seems to be foolish, I saw my computer rendering jobs of much higher complexity than 15.000.000 very well.

So I think it's a bug.

Change History (3)

comment:1 Changed 11 years ago by nhoffmann@…

I think, the bug is that MaxTilesetComplexity? decreases, when a tile with a complexity smaller than the set value gets rendered without errors.

comment:2 Changed 10 years ago by spaetz

The maxComplexity will go down if a tile takes really long to render, assuming that there is swapping going on or the machine is too weak. I suspect those algorithms need some tweaking.

comment:3 Changed 7 years ago by iandees

Resolution: wontfix
Status: newclosed

Cleaning aging tickets.

Note: See TracTickets for help on using tickets.