You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are currently 4 groups of SQL/NoSQL queries running for the load. The switches on the control panel allow you to enable and disable each group for each database.
You can see these queries in the files:
/internal/load/mysql.go
/internal/load/postgres.go
/internal/load/mongodb.go
Help is needed to improve these queries so that they are more varied and their complexity grows with each switch.
The following logic is now in place:
Switch 1: Get an random row from the Repositories table (200 rows). Write this row to the test table. Delete a row from the test table.
Switch 2: Get an random row from the Pulls table (40000 rows). Write this row to the test table. Delete a row from the test table.
Switch 3: SELECT repo FROM (SELECT DISTINCT repo FROM pulls) AS uniq_repos ORDER BY RAND() LIMIT 1
Switch 4: SELECT data FROM pulls WHERE STR_TO_DATE(JSON_UNQUOTE(JSON_EXTRACT(data, '$.created_at')), '%Y-%m-%dT%H:%i:%sZ') >= NOW() - INTERVAL 3 MONTH LIMIT 10;
I'd be happy to hear your suggestions.
Dataset currently includes JSON documents with repository and pool-request data. JSONs have many fields. I can publish a list if needed, but you can see them in the GitHub API. See the JSON example in the Example response section of the page
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
There are currently 4 groups of SQL/NoSQL queries running for the load. The switches on the control panel allow you to enable and disable each group for each database.
You can see these queries in the files:
/internal/load/mysql.go
/internal/load/postgres.go
/internal/load/mongodb.go
Help is needed to improve these queries so that they are more varied and their complexity grows with each switch.
The following logic is now in place:
SELECT data FROM pulls WHERE STR_TO_DATE(JSON_UNQUOTE(JSON_EXTRACT(data, '$.created_at')), '%Y-%m-%dT%H:%i:%sZ') >= NOW() - INTERVAL 3 MONTH LIMIT 10;I'd be happy to hear your suggestions.
Dataset currently includes JSON documents with repository and pool-request data. JSONs have many fields. I can publish a list if needed, but you can see them in the GitHub API. See the JSON example in the Example response section of the page
It is possible to change the table layout, for example to add additional columns. Or additional tables, for example with comments on pull-requests.
All reactions