26 lines
4.3 KiB
JSON
26 lines
4.3 KiB
JSON
{
|
|
"schema_version": 1,
|
|
"saved_at": "2026-08-07T05:08:28.484838Z",
|
|
"content_sha256": "f0c3f879ef85d2e0e63ae4debba499159371abbdb6e029bbcdbd8a2ac9066c32",
|
|
"result": {
|
|
"title": "Ratenbegrenzungen und Abfragegrenzwerte für die GraphQL-API - GitHub Enterprise Server 3.16 Docs",
|
|
"url": "https://docs.github.com/de/enterprise-server@3.16/graphql/overview/rate-limits-and-query-limits-for-the-graphql-api",
|
|
"snippet": "Die GraphQL-API von GitHub hat bestimmte Einschränkungen, um übermäßige oder missbräuchliche Aufrufe der GitHub-Server abzufedern.",
|
|
"content": "Diese Version von GitHub Enterprise Server wurde eingestellt am 2026-07-01 . Es wird keine Patch-Freigabe vorgenommen, auch nicht für kritische Sicherheitsprobleme. Für bessere Leistung, verbesserte Sicherheit und neue Features aktualisiere auf die neueste Version von GitHub Enterprise Server .\nWende dich an den GitHub Enterprise-Support , um Hilfe zum Upgrade zu erhalten.\n\nRatenbegrenzungen und Abfragegrenzwerte für die GraphQL-API\n\nDie GraphQL-API von GitHub hat bestimmte Einschränkungen, um übermäßige oder missbräuchliche Aufrufe der GitHub-Server abzufedern.\n\nAls Markdown kopieren\n\nIn diesem Artikel\n\nPrimary rate limit\n\nRate limits are disabled by default for GitHub Enterprise Server. Contact your site administrator to confirm the rate limits for your instance.\n\nIf you are a site administrator, you can set rate limits for your instance. For more information, see Configuring rate limits .\n\nIf you are developing an app for users or organizations outside of your instance, the standard GitHub rate limits apply. For more information, see Rate limits and query limits for the GraphQL API in the GitHub Free documentation.\n\nNode limit\n\nTo pass schema validation, all GraphQL API calls must meet these standards:\n\nClients must supply a first or last argument on any connection .\n\nValues of first and last must be within 1-100.\n\nIndividual calls cannot request more than 500,000 total nodes .\n\nCalculating nodes in a call\n\nThese two examples show how to calculate the total nodes in a call.\n\nSimple query:\n\nquery {\nviewer {\nrepositories(first: 50 ) {\nedges {\nrepository:node {\nname\n\nissues(first: 10 ) {\ntotalCount\nedges {\nnode {\ntitle\nbodyHTML\n\nCalculation:\n\n50 = 50 repositories\n50 x 10 = 500 repository issues\n\n= 550 total nodes\n\nComplex query:\n\nquery {\nviewer {\nrepositories(first: 50 ) {\nedges {\nrepository:node {\nname\n\npullRequests(first: 20 ) {\nedges {\npullRequest:node {\ntitle\n\ncomments(first: 10 ) {\nedges {\ncomment:node {\nbodyHTML\n\nissues(first: 20 ) {\ntotalCount\nedges {\nissue:node {\ntitle\nbodyHTML\n\ncomments(first: 10 ) {\nedges {\ncomment:node {\nbodyHTML\n\nfollowers(first: 10 ) {\nedges {\nfollower:node {\nlogin\n\nCalculation:\n\n50 = 50 repositories\n50 x 20 = 1,000 pullRequests\n50 x 20 x 10 = 10,000 pullRequest comments\n50 x 20 = 1,000 issues\n50 x 20 x 10 = 10,000 issue comments\n10 = 10 followers\n\n= 22,060 total nodes\n\nQuery optimization strategies\n\nLimit the number of objects : Use smaller values for first or last arguments and paginate through results.\n\nReduce query depth : Avoid requesting deeply nested objects unless necessary.\n\nFilter results : Use arguments to filter data and return only what you need.\n\nSplit large queries : Break up complex queries into multiple simpler queries.\n\nRequest only required fields : Select only the fields you need, rather than requesting all available fields.\n\nBy following these strategies, you can reduce the likelihood of hitting resource limits and improve the performance and reliability of your API requests.",
|
|
"content_type": "text/html",
|
|
"query": "Wie können Rate Limits in GraphQL-Servern implementiert werden?",
|
|
"language": "de-DE",
|
|
"round": 1,
|
|
"fetched": true,
|
|
"relevant": true,
|
|
"relevance": 0.4731428571428572,
|
|
"source_quality": "reputable_secondary",
|
|
"source_quality_score": 0.736,
|
|
"actionable": true,
|
|
"covered_gap_ids": [
|
|
"KG-001"
|
|
],
|
|
"assessment_reason": "Die Quelle ist identisch mit der vorherigen, nur mit einer leicht unterschiedlichen Version des GitHub Enterprise Servers. Sie beschreibt ebenfalls die Ratenbegrenzungen und Abfragegrenzwerte, aber nicht die Implementierung von Rate Limits in GraphQL-Servern."
|
|
}
|
|
}
|