Overpass API developpement

Text archives Help

Re: [overpass] Oversized message in log file

Chronological Thread 
  • From: Roland Olbricht < >
  • To:
  • Subject: Re: [overpass] Oversized message in log file
  • Date: Thu, 5 Sep 2019 07:24:33 +0200


I'm sorry for the longtime silence. I'm the maintainer of Overpass API,
and apparently the question looked like so technically involved that
noby else has attempted to answer.

1. For a particular query I have I see the following line in the
'Oversized: runtime x seconds, size 541110848 bytes in line 1, statement

I would like to suggest to turn off size limits on the local instance.
While there is a good reason to have size limits on the public instances
(because there really are clients with runaway scripts and often enough
so) to protect the sane from the insane users there is no benefit in the
limits system if you are the only user.

You can call
dispatcher --space=1000000000000
or with any other very high number (one US-trillion (=10^12) intended
here) and then use huge maxsize values on each query.

From reading some of the docs and other user's experiences I was looking
to try the maxsize parameter with the query.

However, when I run the same query -still without maxsize parameter-
against another instance of overpass, there is no such message and the server
responds to the query.

Both instances, have 8G RAM.
The differences between the two instances are:

b. Server with error in transactions log is the planet database
Server without error is a local region.
The query is identical to both servers.

Yes, the database sizes do make a difference. This can for some queries
happen even if the final outcome is identical.

The process counts at each step which number of objects it is expecting.
If there are too many objects anticipated then the process is aborted.
If there is more data in the database then the process might expect to
read more data.

To be more precise: the scheduler for queries gives reasonably small
regions (bounding boxes, around, areas) precedence over other criteria.
If you are searching with a small bounding box within the loaded
regional area then there should be no difference. The tipping point for
small is about one square degree.

On the other extreme, if your search criteria is something like a
globally present tag then the estimation is for a good reason higher.
The scheduler only takes into account on (the most prospective)
criterion because combination effects between multiple criteria are
beyond reasonable effort for an estimation.

a. Server with error in transactions log is dispatcher version
Server without error in transactions log is dispatcher version

No, the two release only differ in that error messages have quotation
marks escaped.

-->Why doesn't/didn't overpass allocate the available RAM

Please see above: the purpose of the limit system is to avoid harming
sane by insane users on the public instances. The estimations for that
purposes are rather geared to determine orders of magnitude, not precise

Best regards,


Archive powered by MHonArc 2.6.19+.

Top of page