This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] Why did I get "Over the limit on number of results"?
- Previous message (by thread): [atlas] Why did I get "Over the limit on number of results"?
- Next message (by thread): [atlas] Segmentation fault (core dumped)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Robert Kisteleki
robert at ripe.net
Wed Oct 25 14:46:51 CEST 2017
Hi, On 2017-10-25 14:16, Wouter de Vries wrote: > Hi Eduardo, > > There are also limits on the number of results that you generate per > day, called the "Daily measurement result flow". This could be what you > are describing. > > The limits are shown at https://atlas.ripe.net/atlas/user/ > > Best, > > Wouter Indeed that page describes the limits for a particular user. There's more documentation available at https://atlas.ripe.net/docs/udm/#rate-limits. Let me perhaps explain a bit more of the motivation. We started off with putting hard limits, besides other things, on: a) the number of concurrent measurements a user can b) the number of probes that can be involved in a single measurement c) the total amount of credits one can spend per day A year or two ago we introduced a "daily measurement result flow" (d), with the intention of that it can ultimately replace (a) and (b), perhaps even (c). The idea behind this is that from the resource use point of view it shoould not matter (*) if one runs 1 msm with 10000 probes or 100 measurements with 100 probes each -- what matters is the total output the user is requesting from the system. BTW (a), (b) and (c) are hard numbers, (d) is an estimate so even though it's more user-friendly, it's more difficult to maintain. We haven't reached the point where (d) is the ultimate limit; mostly because there *is* difference in the (*) part above, for internal reasons. Solving this is a long-ish process, but are making steps to get there. Hope this explains, Robert
- Previous message (by thread): [atlas] Why did I get "Over the limit on number of results"?
- Next message (by thread): [atlas] Segmentation fault (core dumped)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]