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/[email protected]/
2017 and RIPEdb only handles 700 updates per *MINUTE*
- Previous message (by thread): [db-wg] Cleaning up SixXS inet6nums & 400.000++ junk inet6nums from 2a07:7ec0::/29 in the RIPE database
- Next message (by thread): 2017 and RIPEdb only handles 700 updates per *MINUTE*
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jeroen Massar
jeroen at massar.ch
Tue Jun 20 14:22:49 CEST 2017
https://www.ripe.net/analyse/statistics/ripe-database/ripedb-updates (see attached png for the current version as over time it will disappear) shows a nice peak with a max of 723.47 updates. Thus either the software is really bad, the updates are rate limited, or the queries are so high that no further performance is to be expected. As alluded to in the other thread, if there was less junk (those 400k inet6nums for instance) then likely this would all scale better.... Are the RIPE DB-WG chairs still actively involved in the maintenance of the RIPE Database!? As two of the co-chairs are working for RIPE NCC, are they able to tell why such a process is slow and why these problems that are being raised over and over on the various lists are not being resolved? Greets, Jeroen -------------- next part -------------- A non-text attachment was scrubbed... Name: whoisupdates-day.png Type: image/png Size: 22556 bytes Desc: not available URL: </ripe/mail/archives/db-wg/attachments/20170620/a80e0bf0/attachment.png>
- Previous message (by thread): [db-wg] Cleaning up SixXS inet6nums & 400.000++ junk inet6nums from 2a07:7ec0::/29 in the RIPE database
- Next message (by thread): 2017 and RIPEdb only handles 700 updates per *MINUTE*
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]